Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Gut checking my understanding of workflows in Jira Next-Gen

Scott.Stephan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 12, 2020

Hey y'all,

I'm inheriting a Next Gen project from a former PM and the team has had some issues with reports being tallied incorrectly. I wanted to go back to basics and make sure I fully understand the underlying principles of Jira with regard to the lifecycle of a task. If y'all wouldn't mind making sure I'm correct:

  • The "Story Point Estimate" on a Story should be the sum of any Sub-Tasks' SPEs
  • Whenever a Sub-Task is closed or a new one is added (A no-no, but it happens) or it's estimate is changed, the SPE on it's parent Story should change
    • This requires a PM to go in and manually change, Jira does not sum this
  • When a Story has no open sub-tasks, its SPE should be 0
  • The only number that matters to reporting and burndowns is the SPE
  • If we want to track the original estimate vs. remaining work, we'd need to add a Custom Field like "SPE at Sprint Start" and manually track that (or view it in the history)

My next question:

  • Should a story's SPE be set to 0 before or after it goes to done?
    • Atlassian support has indicated that if the SPE goes to 0 after it hits Done, it won't be counted as Done in the burndown

 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events