a customer currently has a problem which could not be comfortable solved by tempo timesheets, but maybe some has a different point of view to help me out.
Possible solutions I can think of:
I am quite surprised to see that the issue type is not included in the report, as this would seem to be the easiest solution (filtering the report would even be better).
But maybe there is a fourth solution which I cannot see at the moment...
Any input is appreciated!
Thanks in advance
the issue type is included in the Excel and the XML export. If you have Tempo account as a Jira custom field you only need to choose the Account once, when you create the issue. In case this is done wrong to start with (only the accounts connected to the Issue are available) you can edit the choice within the issue. This account information can be included in the export.
Please take a look at https://tempoplugin.jira.com/wiki/display/TEMPO077/Configuring+Fields+and+Properties for more information.
Hope this helps
it would be great to be able to associate a account to a project / issues type.
I have a support and maintenance service desk project, Change requests and service request are associated with the maintenance element of the contract and incidents with the support element, I would like to automatically set the tempo account to each issues type.
The feature we are looking for is to group by a linked issue type, not just any issue type. For example, there is currently a group by Epic option, but we have a different issue type used for linking issue types to a billing item. And we want to basically group by "Billing IssueType" which is set up similar than Epics. So all of the issues should have a Billing issuetype linked and we want to group all issues (and work on those issues) on that linked issuetype.
I'm was disappointed to see that issue type wasn't one of the first grouping options available. This is really how we want to report up our hours. Isn't issue type one the primary ways you would want to roll up hours by employee? I don't want to have to turn them into accounts just for the reporting, but I did also think of that as did the original poster here.
In the documentation there is some strange language about grouping in reports, " Items are organized according to Jira hierarchy." Can we change that hierarchy? Where is that defined? What is the current recommendation for this?
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event