You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Figured others have run into a similar issue -- there doesn't seem to be a straightforward way to show critical path/issues without float in Jira. Does anyone know of a way to circumvent this through an automation rule, add-on, etc.?
@Arlene_Amaya What about using Story point on issues as Critical path ? I mean sort issues by Story Points, as more story point on issues more critical is the issue, am i wrong ?
HTH
Nicolas
Hi Nicolas, we already use story points as a measurement of effort. However, we want to use a critical path indicator to show which tasks need to be done on time (a delay in task = delay in project). Some tasks may take significant effort (as calculated by many story points), but have a flexible due date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So what about using a mixture of story points and due date ? more SP and closer due date => more critical path ?
HTH
Nicolas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.