Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Tracking the source of demand & effort required

Peter Norris
Contributor
March 4, 2025

We currently use a "Demand" ticket as a way for teams to log requests with other, internal teams. Following that ticket, a number of Epics or Stories may be spawned off it.

I've had a request to be able to log the initial estimate of effort in the Demand ticket, and then add up the Story Points associated to the actual work items that delivered the work - and then have the ability to log the total effort back in the original Demand ticket.

This way the team doing the work can see WHERE their demand is coming from based on actual effort required, and as a by-product, how ACCURATE their original effort was.

Any thoughts on best practice for doing this?

I'm open to scrapping the current way of working; really looking for best practice on how this is commonly accomplished.

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, team '25, conference, certifications, bootcamps, training experience, anaheim ca,

Want to make the most of Team ‘25?

Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.

Learn more
AUG Leaders

Upcoming Jira Events