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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Delivery Status/Progress

Kasia Karska _HeroCoders_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Apr 14, 2023

Hi Group,

Wondering how you are Guys managing the Delivery related list in JPD. What I'm specifically interested in is:

  • do you use statuses to indicate which potential solutions are taken into consideration?
  • how do you manage abandoned or on-hold solutions on an idea that is partially delivered - do you split the idea, mark it as done or keep it in evaluation?

Would appreciate any tips that come to your mind.



Hey @Kasia ,

  1. We don't create delivery tickets until we've committed to building the thing. In my view, developers already have enough to think about without knowing if they need to think about tickets we haven't committed to doing. We use a field in the idea called Product Stage to indicate how far along in our problem/solution process and idea is - once that reaches a certain stage of definition, we'll expose it to developers for input and creation of tasks & epics for the stories
  2. It depends on a few factors.
    1. Abandoned ideas get split off and marked as removed
    2. If there is a small increment to complete, we'll usually leave it on the same idea and make sure the engineers come back to finish it, or
    3. If it's large enough, we'll split it into it's own tickets and add it back to the sprint backlog for review.
    4. There's no hard and fast rule here as your delivery constraints (time, cost etc) all come into play in making a decision about that particular ticket/feature.

Hope that helps.



Hi Kasia,

we take into consideration all ideas for evaluation, having defined a workflow with an archived status where we can send all discarded ideas/initiatives


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events