JIRA tracking issues by creating reports. It shows total estimate of the project, how many time have been taken by a project. What should be the outcome of the project?
Now my question is: What are the types of reports which have been generated in JIRA.
We can generate following reports in JIRA:
1) Average Age Report:
It shows that how many issues are pending or unsolved. Accordingly it will generate a report and give you the particular picture of the project about pending issues.
2) Issue Created vs. Resolved Issues Report:
By the name we can understand that it will create reports for created issues and resolved issues report which will display whole the scenario of the project and display the work done by the Team.
3) Pie chart Report:
It will display issues status with different colors so we can identify the project status or sprint status easily.
4) Project Pivot Report:
It shows that how much time has been taken by the users for verifying project for the specific period?
5) Recently Created issue Report:
It will display all the detail for recently created issues which shows that how many percentage of the project is completed and how many project is pending.
6) All the dead line of the project have been followed or not, all the issues are solved or it has in progress status this all can be verified by reports.
7) We can create sprint report, Epic Report, Version Report, velocity chart, control chart, cumulative flow diagram too.
Progress Report has been shown from here:
Blue line indicates ideal task remaining and red line indicates actual task remaining.
With the help of Pie chart we can see that different status have been displayed with different colors:
8) It also gives reports of Project status or Sprint status.
1) Average Age Report — Shows the average age (in days) of unresolved issues.
2) Created vs Resolved Issues Report — Shows the number of issues created vs the number of issues resolved over a given period of time.
3) Pie Chart Report — Shows the search results from a specified issue filter (or project) in a pie-chart, based on a statistic of your choice.
4) Resolution Time Report — Shows the average time taken to resolve issues.
5) Recently Created Issues Report — Shows the rate at which issues are being created.
6) Single Level Group By Report — Shows the search results from an issue filter, grouped by a field of your choice.
7) Time Since Issues Report — Shows the number of issues for which your chosen date field (e.g. 'Created') was set on a given date.
8) Time Tracking Report – Shows time to track information on issues for a particular version of a project.
9) User Workload Report * — Shows how much work a user has been allocated, and how long it should take.
10) Version Time Tracking Report * — Shows progress towards completing a given version, based on issues' work logs and time estimates.
11) Version Workload Report * — Shows how much outstanding work there is (per user and per issue) before a given version is complete.
12) Workload Pie Chart Report * — Shows the relative workload for assignees of all issues in a particular project or issue filter.
Related
We are using HP ALM 12.53.193 for issue tracking.
For a progress report of our development activity, I am trying to find out what tickets I worked on within the past month. Primarily, this includes tickets for which my user name was added to the Editors field, or that were marked as Fixed or Closed by me in the given timespan.
I am seeing some promising hints in this forum post that uses SQL to query the AUDIT_LOG table. Likewise, this [sqa.se] post suggests an SQL script for an Excel report.
Unfortunately, when I click New Business View Excel Report in ALM, I am asked to upload an Excel file for some reason, so I am not sure how to proceed from there to entering my SQL.
I have also tried creating a report with the New Project Report command (i.e. I am also ok with a non-scripted solution, if that is the way to go in ALM). However, it seems I can only show the filtered contents of single tables (e.g. Defect) there (the "Cross Filter" feature does not let me choose another entity (e.g. the Audit Log) for cross-filtering my defects with).
How can I retrieve that data from ALM?
I am not entirely sure SO is the right site for this question, although I consider HP ALM a "software tool(...) commonly used by programmers". Please migrate if it is deemed a better fit for another site.
My organisation recently applied an update to TFS 2015 (14.102.25423.0 according to the 'About' page of the web interface) that resulted in the 'My Work' tab in Visual Studio 2015 taking up to one minute to populate. I played around with the queries and managed to narrow the problem down to population of the 'Incoming Requests' section of that tab. Under the hood, this is executing the following WIQL query.
SELECT [System.Id], [System.Links.LinkType], [System.Title], [System.State], [System.Reason], [System.AssignedTo]
FROM WorkItemLinks
WHERE (Source.[System.TeamProject] = #project and Source.[System.WorkItemType] in group 'Microsoft.CodeReviewRequestCategory' and Source.[System.AssignedTo] <> #me and Source.[Microsoft.VSTS.Common.StateCode] <> '1')
and ([System.Links.LinkType] = 'System.LinkTypes.Hierarchy-Forward')
and (Target.[System.WorkItemType] in group 'Microsoft.CodeReviewResponseCategory' and (Target.[System.AssignedTo] = #me or Target.[Microsoft.VSTS.Common.ReviewedBy] = #me) and Target.[Microsoft.VSTS.Common.StateCode] <> '2')
ORDER BY [System.CreatedDate] desc, [System.Id] mode(MustContain)
I've reproduced the slowness using the TFS REST API described in https://www.visualstudio.com/en-us/docs/integrate/api/wit/wiql (passing the WIQL query above in the body of the POST request).
The following code review selectors are slow to populate: My Code Reviews & Requests, Incoming Requests.
The following code review selectors are fast to populate: My Code Reviews, Recently Finished, Recently Closed.
The problem is occurring for all users, not just my user.
No one on the team has more than a few code reviews open at any one time.
The problem started occurring practically overnight i.e. on Friday the queries were completing in a second or so, on Monday the queries were taking up to a minute.
Our TFS environment is hosted on Windows Server 2012 (non-R2).
Our TFS environment is backed by SQL Server 2012, SP3 (11.0.6020).
The upgrade to TFS2015.3 was completed as per Microsoft instructions and no issues were encountered and there are no messages in the logs to indicate anything is wrong.
Does anybody have any suggestions about what might be causing this slowness and what can be checked in order to narrow the performance problem down further?
The Team Explorer in Visual Studio provides a dropdown selector for specifying which state of code reviews one wants to list. The available choices are:
My Code Reviews and Requests (open)
My Code Reviews (open/mine)
Incoming Requests (open/others)
Recently Closed (closed)
Recently Finished (finished)
( Annotated each entry above with the state and ownership for clarity.)
According to the description of your performance issue, since this is occurring for all users, seems there are a large number of code reviews in your team. When you open the My work tab , the loading of the various code reviews cause a performance issue.
For this situation, you can try this workaroud: switch over to my code reviews in that Team Explorer drop down selector. After this, please double check whether the issue is gone or still exist.
Answering my own question here... My organisation ended up escalating this through Microsoft and eventually found that there was an issue with out of date statistics causing bad query plan generation. The query that was used to retrieve code review details was taking more than 60 seconds each time it was run.
The queries below will most likely make a significant different to performance if you encounter the same problem.
use <collection db name>;
UPDATE STATISTICS [dbo].[tbl_WorkItemCoreLatest] WITH FULLSCAN
use <collection db name>;
UPDATE STATISTICS [dbo].[tbl_WorkItemCustomLatest] WITH FULLSCAN
For reference, there's a duplicate of my original post on Microsoft Connect here: https://connect.microsoft.com/VisualStudio/Feedback/Details/3107261. The comments from Microsoft in this post indicate a number of people were seeing similar behaviour.
I just want to create report from Jira (Chart report showing total bugs of weekly report for 2 projects) I tried using time since report.Generated graph displayed total bugs for the 2 projects, But I want 2 projects name with each issues associated with project for each day.Is there any way to get the report?
I guess you are in search of a Dashboard. Dashboard will keep you update after regular interval about the status of the project. For creation of a dashboard you will need to create a filter first and then the Dashboard.
Create filter according to your requirements. i.e. search issues logged by QA in particular time period, in particular sprint etc.
This link will help you https://university.atlassian.com/uac/2.0/courses/end-user/jira/v60/search-and-filters/save-and-share-filter#/lesson-content-header
After creation of the Filter create a dashboard.
Follow steps mentioned in below link https://university.atlassian.com/uac/2.0/courses/end-user/jira/v60/dashboards/create-share-customize-a-dashboard
https://confluence.atlassian.com/display/JIRA/Customizing+the+Dashboard
Hope this helps you.
Background
I have developed a SSAS cube that works well for most of my organization's purposes. The primary method of users interacting with this cube is via Excel Pivot Tables.
The Issue
Some of the Pivot Tables created by users have attributes for which their attribute hierarchies take a long time to resolve when the user first clicks on the drop-down box over the field name in the Pivot Table. For instance, the first time a user clicks the drop-down for a field called "Location - County", it takes ~45 seconds for the pop-up box with the list of ~40 counties to show up.
Side Note 1: If I had to guess, it actually seems like SSAS is resolving all field hierarchies in the PT at the same time as the first field that was clicked on because right after this initial resolve, the user can click on any of the fields in the PT and they resolve instantly. Said another way, the first field clicked on always takes ~45 seconds to resolve.
Side Note 2: The next time the user clicks on any of the field drop downs, it resolves almost instantly which I am assuming is because of caching.
The question
Why does it take SSAS so long to resolve some attribute hierarchy lists? It seems to me like this should always be instantaneous?! Doesn't SSAS build all attribute hierarchy lists ahead of time (i.e. during cube processing)?
Many thanks for any light you can shed on this issue for me.
Regards, Jon
1/20/15 Update: Adding Trace Files per Request: Zipped Trace Files. I included all EventClasses just to be sure, but if you need me to run again with only the EventClasses requested below I could.
"Trace of DAR Cubes Project - Test (from service restart).trc" - I restarted AS and immediately refreshed my PT, and recorded the traced events in this file.
"Trace of DAR Cubes Project - Test (after one refresh).trc" - After refreshing the Excel PT as described above, I closed Excel, reopened the same PT, and refreshed again. I expected a much faster refresh, but was surprised with almost the same ~35 second wait. If I keep Excel open between refreshes, it only takes ~2 seconds. This makes me wonder if Excel is caching the results somehow? Which would be weird b/c I thought all the logic and caching took place on the server side.
I am trying to use the Version One api to get the project and sprint burndown charts.
I am reading this page but I am just getting confused.
Has anybody done something similar and have any tips for how to hit the api to get what I want?
The VersionOne api does not serve images or chart specific data. You can use the query language and the rest endpoint to produce the data that is needed for a burndown. You would need to be able to read/parse the data and produce a graph yourself.
With that being said, a burndown graph compares how much closed estimate versus how much open estimate and graphs that over time. So you need to know three pieces of data: open estimate, closed estimate, and time. You'll also want to limit it to a certain project (and it'd children).
This should get you close to the data you need for a project burndown:
http://<host>/VersionOne/rest-1.v1/Data/Timebox?where=Schedule.ScheduledScopes='Scope:1055'&sel=Name,BeginDate,EndDate,Workitems:Story[AssetState!='Closed'].Estimate.#Sum,Workitems:Story[AssetState='Closed'].Estimate.#Sum&sort=+EndDate
Be sure to change Scope:1055 to the project oid that you're interested in.
This is how I got there. First I was thinking "well you need to sum up a bunch of story estimates" so I thought I'd do a historical query of stories:
http://<host>/VersionOne.Web/rest-1.v1/Hist/Story?where=Scope.ParentMeAndUp='Scope:1055'
But quickly found that you cannot aggregate on your root. What that means is if I want to sum up estimate, I need to use something else like Project (scope) to get at the data:
http://<host>/VersionOne.Web/rest-1.v1/Hist/Scope/1055?sel=Workitems:Story[AssetState!='Closed'].Estimate.#Sum,Workitems:Story[AssetState='Closed'].Estimate.#Sum,ChangeDate
The problem with this query is is gives you what the closed versus open estimate looked like at weird intervals; namely whenever the project changed. So it wouldn't make a very nice looking graph.
But as you know VersionOne has a concept of Iterations and Schedules that are associated to a project, and stories are associated to iterations. So I used that as a root to query for and aggregate story estimates, and limit the data to projects that use that schedule.
The data that is produced is more regular (grouped by iteration) and contains correctly aggregated estimate data.
So what is left? You'll have to aggregate the aggregation of estimate data to get a total estimate number for your project. Then you'll need to produce a graph (maybe bar or line) where each data point is at the end of an iteration. You'll keep a running total of closed estimate and add that to the iteration's total to produce the data point.
You need to do multiple queries to produce a burndown. First find the date range for the burndown:
/Data/Timebox?sel=BeginDate,EndDate&where=Name='X'
Now for every day the date range, sum up the ToDo hours as of that point in history:
/Hist/Timebox?asof=2013-08-09T23:59:59&where=Name='X'&sel=Workitems[Team.Name='Y';AssetState!='Dead'].ToDo.#Sum
The API and documentation are excellent. If you are interested in seeing the code for some custom reports, check out https://github.com/timothypratley/vone/blob/master/src/vone/models/queries.clj (the code is in Clojure). There is a burndown, cumulative flow, and more :)
There is now a "recipe" to query for burndown data that works with the query.v1 API endpoint.