Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,294,790
Community Members
 
Community Events
165
Community Groups

Tempo accounts/reports by issue type

Hello,

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.

Situation is:

  • Projects only have 2 issue types: Bug and Service
  • For each customer there are two tempo accounts refering to these issue types (as they are billed differently)

Problem is:

  • There is the possibility to choose the wrong tempo account for an issue
  • The entered information about account is redundant, as it is already identified by the issue type

Possible solutions I can think of:

  • Assign an account in tempo to an issue type and not to a project
  • Preselect an account depending on issue type
  • Include issue type in timesheet export and sort it out there

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
Thomas

4 answers

1 accepted

Hi Thomas,

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

Susanne (Tempo)

You could also create a post function or use issue bulk changes to keep the type and account in sync.

Thanks, I totally didnt see the issue type in the export as it was hidden somewhere in the middle.

About the other things we can talk on thursday - if you are in Wiesbaden...

BUMP

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?

Bump from me too, this would be a great filter to have.

Bump from us to. 

Very annoying to not have issue type in UI, I know I can get export but it would be so nice to just get straight out of JIRA

Bump - 2021 and still no progress on that? 

Any updates on this issue?

 

Thanks.-

Hi Thomas,

We are aware of this limitation and and working on solutions to it. Thanks for the feedback.

Viðar, Tempo

If you mean assigning an account to an issue type: that would be great!

it would be great to be able to associate a account to a project / issues type.

 

I.e 

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.  

Bump! Still nothing after 7 years?

Hi Bram,

we are getting there. Please look into the feature request.

BR

Hi @Alexander Eck _Tempo_ ,

 

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Apps & Integrations

Marketplace Partner Spotlight: AppLiger

This month the spotlight is on AppLiger. We caught up with Pavel Pavlovsky, CEO and Product Manager, to learn how the company started and what fuels the team's creativity.    Atlassian:...

349 views 0 7
Read article

Community Events

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

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you