Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

New Issue View and Time Estimates

Our use case is when we are sprint planning, we will collaboratively plan out an issue using sub-tasks, and create hour estimates for these tasks, setting our original estimates and the remaining hours for these tasks.  

Prior to sprint planning, team members will add tasks and estimates they think are necessary in order to streamline the planning meeting.

Occasionally, an estimate needs to be changed either because of team discussion or because it was entered incorrectly.  There is a Time Estimate field on the new issue view, and we can change that, however, it only sets the remaining hours when it is initially set.  If we update this number from 2 to 6, the remaining hours stay at 2, while the initial estimate changes to 6. 

We are using a pretty vanilla Scrum template for the project, and have the Tempo Timesheets addon for our time tracking.

The only solution we have found is to go to the old view, where we can update the both the original estimate and remaining estimate.  The remaining time can be updated using the tempo panel, but only if you are logging time to the issue, which we don't want to do, nor is it feasible to expect whoever picks up the issue corrects the remaining hours because they remember there was a mistake.

Is there a solution to our problem that we aren't seeing, or is this a known issue that will be fixed?  

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

167 views 6 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