I am trying to work out how to add the fields I need for tempo into the issues in a next gen board. I can see I can add text fields/ drop downs etc but how do I get them to link to tempo for our time tracking and reporting
In classic the Account field is one I can add in easily.
Hi @Laura Phillips,
I do not think it is possible yet for the custom Tempo fields to be visible. I would select the Feedback button in the Next-Gen project to let Atlassian know about this limitation.
Currently, you have to go into the Next gen project's Settings > Apps > Accounts, add the accounts you want your users to have access to in the project and when time is logged the account will be selectable. You can also select a default account for work-logs to automatically attribute themselves to.
Hope this helps
This issue has been resolved by now. Atlassian sent a newsletter on 2020-07-31 introducing the new feature of using fields provided by third-party apps in next gen projects.
With this information it is possible to add for instance the account field to your next gen ticket views. Everything is working now as expected and like it worked before in classic Jira projects.
Original message of the newsletter:
|Next-gen project owners can control the fields provided by third-party apps|
|Just a friendly heads up from the Jira Cloud team.|
|Soon, next-gen project owners will be free to use or ignore app fields provided by your site's third-party apps.|
|As a Jira admin, you can view and edit a next-gen project's settings. To toggle on or off third-party apps in your teams' next-gen projects:|
|1. Navigate to the next-gen project you want to power up.|
|2. Go to Project settings > Apps > App fields.|
|3.Toggle the app whose fields you want to use.|
|When you toggle on a field, you can add it to your project's issue types by going to Project settings > Issue types.|
@Florian Beese do you have a link to this newsletter? I can't find anything in my mailbox, so I'm wondering if I don't have all relevant newsletters subscribed. :)
The two related Jira Issues where you also commented are both in status Gathering Impact. I think the communication from Atlassian and Tempo in this case could be a lot better.
@Sebastian Esch You can find a web representation of the newsletter here:
I am very happy, that it finally works now. From my point of view there is nothing left unaddressed.
When an Account has been linked with the project you can add it to the issues in the next-gen projects by bulk editing the issues ( even if the Account will not show in the Issue directly). All worklogs made on this issue will then be linked to this Account.
To have a selection of Accounts ( so you can overwrite the set Account or if no Account is set), you need to create a work attribute of type Account (https://tempo-io.atlassian.net/wiki/spaces/THC/pages/172458294/To+configure+accounts+as+work+attributes).
You have then an additional field in the Log work dialog that allows you to select any of the Accounts that have been linked to the next-gen project
Although this particular issue has been annoying and breaks one of my own essential workflows, in all fairness, I feel the need to defend Atlassian in this one, as I feel they have handled the rollout of next-gen in exemplary fashion.
We have a public roadmap we can consult, their UX designers book time with actual users (myself being one of them) for feedback sessions, they published their design system, their team playbook for how they manage teamwork sessions and everything. They're also quite active on the forums and their support desks.
In the end though, any development team will at times make decisions (and/or mistakes) that will rustle someones feathers. Hopefully, they will respond rapidly and offer a fix or viable workaround.
Hi @Mark Mühlberger ,
As mentioned in my comment above ( Jan 21 2020) you will need to contact Atlassian directly about this, as Tempo has no control over the fields that can be added to Next Gen issue screens or the bulk edit option in JIRA.
Without either the option to add the Account field to an issue or bulk edit the issues, issues can not be linked directly to an Account.
You can link worklogs to accounts by using Account as work attribute ( this work attribute is global and will then show in the Tempo Log Time dialog independent if you are logging on a Next Gen project or a Classic project), see also https://tempo-io.atlassian.net/wiki/spaces/THC/pages/172425270/Configuring+Work+Attributes+-+Tempo+Cloud
The Account work attribute in the Log Time dialog is then populated with the Account(s) that are linked to the Projects (https://tempo-io.atlassian.net/wiki/spaces/THC/pages/202375235/Linking+Accounts+to+Jira+Projects+-+Tempo+Cloud, Linking in Accounts Configuration)
...ollected feedback from users around the lack of shortcuts, and we’re here to address that: In next-gen projects, I miss the keyboard shortcuts badly. This is particularly true on the Board, but also i...
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