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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Advanced roadmaps - Creating an issue with Original estimate populated

Hi,

 

I would like to track both Original and Remaining estimates for all of my issues. Use case I have question about is how can I set/update both of the estimates when working in Advanced roadmaps. Please see my examples below:

 

1. Jira - creating an issue and entering Original estimate sets Remaining estimate to the same value - expected and ok

Screen Shot 2021-03-12 at 11.24.30.png

 

2. In Portfolio ("old view") there is an option to set/update both values - expected and ok

Screen Shot 2021-03-12 at 11.25.48.png

 

3. Advanced Roadmaps there is option to set/update Remaining estimate, but I don't see any way to add/update Original estimate. Also tried creating issue from Advanced roadmaps and entering only Remaining estimate - that results in Original estimate being empty. Is there any option to solve for this?

 

Screen Shot 2021-03-12 at 11.30.06.png

 

1 answer

0 votes
Dave Atlassian Team Mar 14, 2021

Hi @Anita Cacic

I would recommend that you add the the "Progress (days)" field to your plan as well as the "Estimates (d)" field.

If no original estimate has been set on an issue then giving the Estimate field a value and saving back to Jira will set the original estimate. It is not possible to log time spent on an issue through the plan (it is expected that this will be done on the issue screen) but you can view the progress of hours logged against the original estimate using the Progress field.

If you change an existing value on the Estimate field in a plan and save that change then this will set that value as the remaining time left to complete.

Screen Shot 2021-03-15 at 10.18.58 am.png

I hope this helps but please let me know if you need any additional information or if I've not understood the question properly!

Regards,

Dave

Hi Dave,

this If no original estimate has been set on an issue then giving the Estimate field a value and saving back to Jira will set the original estimate. is what I'm unable to do. 

 

Here are my steps:

1. In advanced roadmaps created new Task and entered 1d in Estimates (d) field

2. In Progress (days) I can see 1 out of 1 days remaining and that is expected

3. When I commit changes and open the same issue in Jira I see that Original estimate field is empty

 

Can you please double check those steps?

 

Advanced roadmaps:

Screen Shot 2021-03-15 at 10.24.45.png

Jira:

Screen Shot 2021-03-15 at 10.27.01.png

Like Dave likes this
Dave Atlassian Team Mar 15, 2021

Hi @Anita Cacic ,

That looks like the older issue details screen - is that a Cloud platform screenshot? It also looks like you're using the Tempo add-on application.

Compare with these screenshots:

Screen Shot 2021-03-15 at 8.40.55 pm.png

Screen Shot 2021-03-15 at 8.42.23 pm.png

Having said that... I have subsequently noticed that you are absolutely correct that the "Original estimate" field (which I didn't have displayed on my issue screen) isn't being updated - the plan is only setting the time remaining (which is what is also used to initially populate the time remaining in the time tracking field).

So actually you're completely correct that the plan is not updating the Original Estimate field (I had just been focused on the time tracking field) - I got confused with how it works and I apologise for misleading you with my previous response - I'm so sorry!

Regards,

Dave

Hi @Dave thank you for your response.

 

Can you please clarify just the next steps? Is this issue with Original estimate something that is on roadmap? Is there any workaround except just creating issues in Jira if I need to track Original estimate as well? 

Like etienne Borella likes this
Dave Atlassian Team Mar 15, 2021

Hi @Anita Cacic ,

Unfortunately this isn't something that is on our roadmap and I've actually validated that this is working as intended (I had just misremembered how it worked unfortunately). In terms of a workaround, it's not going to be possible to view the Original Estimate field directly in the plan but if you want to track it within Jira issues then setting it directly on the issue would be the way to do it. Could you provide some more information on how you would want to track that original estimate field and what you'd do with the information? Is it so that you can check if the original estimate has been exceeded or changed?

Regards,
Dave

Hi @Dave ,

 

I'm ok with it's not going to be possible to view the Original Estimate field directly in the plan . 

 

What I am confused about is the following

- when creating issue in Jira with Original estimate empty, but Remaining estimate populated with 1d the result is both Original and Remaining estimate populated with 1d - and that is ok.

- when creating issue in Advanced roadmaps with Remaining estimate populated with 1d the result is Original estimate empty and Remaining estimate populated with 1d

 

What is the reason why the same logic is not applied when creating issue in Advanced roadmaps with Remaining estimate populated?

 

Regards,

 

Anita

Like Dave likes this
Dave Atlassian Team Mar 16, 2021

Hi @Anita Cacic,

I asked around and this is actually something that goes back many years (before most of the current team started working on Portfolio / Advanced Roadmaps). The most likely reason is one of expediency / simplicity. There is no reason why we wouldn't make the change to additionally set the Original Estimate if it is empty when creating an issue from a plan - but the reality is that this isn't on our current roadmap and isn't a huge priority for us (relative to other features and platform support work).

That's not a great answer I know, but an honest one at least. I wouldn't want to promise a change that we're unlikely to deliver in the near future.

Regards,

Dave

Thank you for your support @Dave 

Like Dave likes this
Dave Atlassian Team Mar 17, 2021

No worries @Anita Cacic - very happy to help, sorry for any confusion I caused with my earlier responses!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

98 views 2 8
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