We are trying to use the Tempo time tracking Fields.
Time Tracking :
estimated: (How do we create an estimated hours for the issue/story?)
remaining: (Remaining hours as marked in the issue) DONE
Logged: (total logged hours inside the issue) DONE
@Sigurd Enghoff are you on Cloud? What does the create issue screen look like? The second screenshot? You won't see "original estimate" on the configuration screen, it will only show as "time tracking" in the configurations. However, when you go to the create/edit screen (actually go create an issue in the project) "Time tracking" will not be on your create/edit screens, instead you will see the "original estimate" and "remaining estimate" fields.
@jan we are currently evaluating tempo for JIRA and running into the same issue. I cannot figure out where or how to set an estimated time. I can set remaining and i can log time, but we will require the ability to estimate the time it will take to complete an item. We are currently using the Next Gen Project.
@Kyle - the "original estimate", "remaining estimate" and "hours logged" are out of the box fields for Jira. They are not Tempo fields. Tempo plugin simply uses those fields in addition to other configurations they provide. I would make sure the "time tracking" is on the Create Screen as well as the edit screens. Also check the permission scheme for the projects. The persons will need to have the permissions for "work on issues" to see or edit those fields.
Here is a starting point for documentation on Jira time tracking fields/configurations. https://confluence.atlassian.com/adminjiracloud/configuring-time-tracking-818578858.html
thanks for the response. Yeah i have tried to go through all the documentation and searched everywhere for just "Estimated Time" and "Original Estimate". One of the key things is that I am attempting to use the Next Gen project which does not have the concept of a create and update screen.
For troubleshooting purposes i was able to get this whole thing to work fine and have the fields show up on a "classic" board.
I just cannot get it to work for a Next Gen project. May be a bug/afterthought for the new project types.
@Kyle you could login to Atlassian support and read this issue. If it's similar to what you are facing, then I would suggest voting and watching it. https://jira.atlassian.com/browse/JSWCLOUD-17248?filter=98153&jql=project%20%3D%20JSWCLOUD%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20next-gen%20AND%20text%20~%20%22original%20estimate%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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