I can't figure out how to make the estimate use time instead of story points. I am sharing this board with a client who thinks in terms of hours billed, not story points. The documentation says to go to the Board Settings but that option is completely missing in my project. This is the documentation page. Also I am using Jira Cloud.
We are kicking off research into original time estimates in the next 2 weeks, so we can build it for next-gen projects!
If you're keen to have a chat with us (we will thank you with a gift voucher for your time), please book a chat with us at https://calendly.com/iteong/jira-software-next-gen?month=2019-10
Note that there will be limited availabilities in my schedule, so if you're keen to chat, please schedule something as soon as you can.
Many thanks and looking forward to chat with you soon!
Product Manager, Jira Software
Hi @Carlos León ,
Add time estimates to your issues Coming in 2020.
@Ivan Teong , I am not finding a time estimate field. Might I not have sufficient rights? A due date tied to an issue is of no value to me when using sprints (not kanban). Due date and points are all I see when I create a new issue type.
disclaimer: I am taking over a next gen project I did not create, and I have not been through the creation process in next gen.
My understanding over the years is that the general flow of agile sprints [as I am familiar w/ it] is that issues are created on the backlog. They are simply captured, may be unassigned, may not have estimates etc.
Issues are either estimated in story points or in hours. Traditionally points is the original tracking mechanism, but many folks wanted to use hours, so in the old version of Jira, hours or story points could be used, and the particular paradigm was selected at the project level. It appears now they are selected at the issue level? Not sure how this works when using sprints.
During backlog review/grooming, issues are given estimates in points or hours, a priority, and an assignee, or else you can't plan a sprint. No issue has a due date, the sprint is the due date, when the issue is pulled into or planned in a sprint.
It would seem to me a good idea to down select (eliminate) options when creating a project depending upon the project options. For example if the project is managed using sprints, offer fields for hours or story points, or both [using both, hours calculate burn down, and story points can be used as a level of estimation risk, and not not for burn down]. If the project is kanban, offer the due date field. But to offer all field types know matter what paradigm a project is using seems unmanageable and is confusing to the end user.
Can someone please help me with the Orginal Estimate field in JIra next-gen. As many of my friends out there says that it's not there in the Jira Next-gen. Few people recommended to create a custom field. I did create a numeric field for Original Estimate, associated it with my respective Kanban next-gen project, however, that filed for is not visible. Am i doing something wrong. Please refer to the attachment and help.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and 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