However it is for me possible to set up and run the Reporter tool for iTunes Connect, I seem not be able to run Detailed Reports and I cannot find a way how to retrieve the data for Subscriptions in the same way as on the webpage for iTunes Connect.
Summary Sales Reports with Sales.getReport of type Summary work fine:
java.exe -jar Reporter.jar p=Reporter.properties m=Normal Sales.getReport 8xxxxxxx, Sales, Summary, monthly, 201605
But Detailed Reports do not work:
java.exe -jar Reporter.jar p=Reporter.properties m=Normal Sales.getReport 8xxxxxxx, Sales, Detailed, Weekly, 20170101
The other thing is to be able to get the subscriptions data to a specific date, e.g. number of subscribers on 12.11.2016.
Thanks in advance for your suggestions!
Notes to self (and those researching reporter tool usage):
I find, overall, for the ever changing reporter tool, the Apple documentation lacks details. For instance in regards to properties file, the Access Token worked before (few day ago) with the argument "Password=" now it is needed to be set to "AccessToken=", however, in the documentation you won´t find guideline how to set properly the Properties File´s Arguments, and, after downloading the reporter 2.1 you realise that the properties file contains the argument "Password=" as well.
Addressing the Subscription reporting, the new Reporter User Guide dated 18.7.2017 contains information how to do this, for Subscriptions and Subscribers, and works fine for me. For completeness, here a piece of code for someone behind a company´s firewall using proxy would run:
java -Dhttps.proxyHost=proxyHost -Dhttps.proxyPort=portNumber -Dhttps.proxyUser=proxyUsername -Dhttps.proxyPassword=proxyPassword -jar Reporter.jar p=Reporter.properties m=Normal Sales.getReport VendorNumber, Subscription, Summary, Daily, 20170105
The above code returns a summary with all running subscription on the selected day.
Otherwise, before running the above code or when problems occur, one clould also check the availability of the reporter service with get status command:
java -Dhttps.proxyHost=proxyHost -Dhttps.proxyPort=portNumber -Dhttps.proxyUser=proxyUsername -Dhttps.proxyPassword=proxyPassword -jar Reporter.jar p=Reporter.properties m=Normal Sales.getStatus
with the positive outcome "Sales and Trends Reporter is currently available."
Related
I'm trying to get to the contacted_at field for all runners on a gitlab instance and get the values inside Logstash.
gitlab.example.com/api/v4/runners/all gives an abbreviated list of all runners, but the details are hidden unless they are called by a specific ID. Is there a way to do this without specifying each and every runner's ID?
GitLab 14.8 (February 2022) comes with:
View read-only runner details in the Admin Area
You can now view the details of a runner in the Admin Area. This new view aims to provide the most valuable information about each runner associated with your GitLab instance. You can view last contact, runner version, and assigned projects, which is now paginated. In the new paginated jobs tab, you can also view a full list of jobs run by the Runner, which helps you view, search, and analyze CI/CD job execution history quickly.
See Documentation and Issue.
This is not what you want, but the associated issue for that GUI feature, issue 347856, includes multiple GraphQL API evolutions which could be of interest.
"Add createdAt to Runner GraphQL API"
"Add editAdminUrl to Runner GraphQL API"
"GraphQL: Add projects property to CiRunner type"
Maybe that means a GraphQL query is now possible to get much more information for all runners, since this is what the GUI is using to display that new list.
And: See GitLab 15.0 (May 2022)
View more details about each runner
Previously, if wanted an at-a-glance view of a runner’s relevant information, you had to switch between screens or even use the API to retrieve the details. Now, administrators can view the runner’s executor, architecture, and platform on the runner’s detail view. These details can help you quickly determine essential details, which are critical for troubleshooting issues or managing day-to-day operations and maintenance tasks.
See Documentation and Issue.
We are using JIRA to work with a team of Developers and a QA team. Currently the 'Dev Team Leader' creates a 'Task' ticket, assigns it to the development member, who work on that ticket and then informs the JIRA ticket number to the QA team, who create a separate QA ticket for testing it. And of the test is pass or failed they inform the DEV team, who either fix it or change the ticket status to 'In Deploy'.
My question is as follows:
Should they create single ticket and use that to do the Development and Testing ? (ie. shift the ticket between the DEV Team and QA Team)
Should the DEV team create a Parent TASK ticket for Development and then assign it to the QA team, who will create a Sub-Task for the Testing and link it to the Parent Development ticket?
Issues:
We need to identify which team member worked on the development
task?
Which team member worked on the Testing ?
How much of tie spent on Development as a whole?
How much of time spent on Testing as a whole?
What is the best way of doing this ?
You only need one ticket or an Issue in JIRA context. Your Project should have a workflow with, for example, the following Statuses: To Do -> In development -> In testing -> from here, the Issue can go in two directions, back to In development if the QA is not satisfied or Done.
When the Issue is moved to the next step, it will/should be assigned to the proper person, i.e. in To Do it's assigned to your project lead or whoever distributes the tasks, In Development it's the developer, In testing the QA, etc.
This is the most widely-accepted way to use JIRA as a ticket tracker. Each transition will be recorded in the Issue Activity Log with the corresponding datetimes, Assignees, etc. You will have access to all the information you've asked for.
It sounds to me like the workflow is in need of granular tracking of development work and testing, where a single ticket (suggested idea) doesn't satisfy.
I found the following design useful:
1. Create a USER STORY that has a set of criteria that needs to be met.
2. Sub TASKS can be created as children of the STORY especially if they need to be worked on by different people.
3. Once all tasks are completed, the USER STORY can be moved to TESTING / IN TESTING (whatever the workflow defines).
4. The QA/QE Engineer then can create TESTS / TEST CASES (children) for the User Stories and and execute them accordingly. Similarly, defects can be filed as BUGS as children of the story.
Ultimately in this workflow the story must meet a set of criteria and level of quality (based on what is acceptable to pass the story for the business) in order to be considered "completed" or ready for release.
I wrote a Rally app to do reporting on TestSets and TestCases. Suddenly today, my app was not getting any TestCases in it's query.
To simplify this, I will take my app out of the equation and I am just running queries with the web service api: https://rally1.rallydev.com/slm/doc/webservice/index.jsp?version=1.40
If I query a TestSet, the TestCases field, which should contain a list of the TestCases in the TestSet, is coming back empty for TestSets that definitely have TestCases. This was working perfectly up until sometime in the last few days (we used the app today and weren't getting any TestCases when the last time we used it, we were and no changes have occurred on our end).
If I look at Test Cases in Track->Iteration Status in Rally and expand the TestSet to see all the TestCases, they show up. So they are there, just for some reason the web service api isn't returning them.
I've spent the last two hours reading the API documentation and searching Google to see if anyone else has had this issue or if anything might have changed that is causing this, but I haven't found anything.
I have confirmed that other objects containing a list of TestCase objects (such as TestFolders) are properly returning a list of TestCases. I have also confirmed that I am able to query the individual TestCases that should be returned in the list. I have also confirmed that I am able to query the TestCaseResult for the particular TestSet and TestCase.
So I am really stumped. It appears as though it's just TestSet.TestCases that isn't working and I am unable to find any specific cause or correlate something unrelated that could be the cause.
Any thoughts?
Rally's DevOps team issued a fix for this issue the evening of 10-jan-2013. TestSet queries through WSAPI should be appropriately hydrated with member TestCases again. Contact Rally Support with any questions or concerns.
This is a bug - Rally's engineering team is aware of the problem and is working on a fix. Please file a Case with Rally Support to report/get status updates on the Defect resolution.
I'm testing out the OpenERP 6.1 web client, and I sometimes have a sales order or other kind of document that gets stuck for some reason. I want to be able to look at the workflow diagram for this document to see exactly where it is stuck.
One example that happened to me was a sales order that had shipped and the invoice was paid, but the sales order still wasn't done. After some digging, I found that one of the procurements was still running.
I can still print the workflow from the GTK client, but isn't there some way to print it from the web client?
I found a couple of ways to get at the screen that lets me edit the workflow, but that's not what I'm looking for. I want to print the diagram that shows the current state of the workflow instance for the open document.
Yes I agree with the Ruchir comment that in web-client you can not print workflow, but I would like to remind that from some of the views we have Process View Implemented which are interactive and Useful to show your business process.
To see how you can use it follow the following link Managing your Sales Quotations This will guide at the end how you can use the Process view.
Like When you Draft your Quotation your Some process Ndoe will be in Red End Color other will be Gray then if you move forward the state will keep on changing, and advantage over here is they are interactive you can jump to specific node related view so you can drive you Sale process very fast and interactively.
Hope this will help.
from webclient it is not possible to print workflow . so for that you have to use GTK client.
I am looking for a way or a plugin so that trac sends me email about the number of new or closed tickets (and some information about these tickets also ) for a specific duration lets say for the last three days.
Basically I need to know how many tickets have been created in last week and how many of them have been closed at the end of week.
Of course the email only should be sent to the admin and not to all the users.
For additional Trac funcionality we have Trac plugins, yes. And the first place to look for them is trac-hacks.org .
The excellent TagsPlugin in use overthere already delivers some hints on resources tagged with notification or notifications. The most comprehensive and mature solution is certainly TracAnnouncer with a just reworked configuration interface providing a highly sophisticated opt-in and opt-out subscription system. Unfortunately digest notification are not integrated today.
Still there are other plugins, that fill in the gap, i.e. check the XMailPlugin. It claims to do configurable instant, daily and weekly notifications, so this may be for you. Since this is a relativly new plugin, you should expect some pending issues, but the author might be very open to your suggestion. If you're becoming a heavy user giving valuable test feedback and a bit lucky too, asking kindly could be enought to make things happen.
There's a slightly different way to solve this problem that doesn't require any plugins. First, create a custom "timeline" view that displays the information that you want. In your example, this would be all "opened and closed tickets" starting from "today" and going back three days. When viewing this custom view, you should see a link at the bottom of the page that says "RSS Feed" (on my system, the resulting URL looks something like this: http://myserver/timeline?ticket=on&max=50&authors=&daysback=3&format=rss). Click on this link to subscribe to the feed using your web browser, email client, or other program capable of reading feeds. Now, you can view the results live at any time. What you can do at this point is only limited by the capabilities of your feed reader app, but most can at least be configured to notify you when the feed is updated.