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

Story breakdown in JIRA

We have a project in which each story requires work on multiple components and environments . Each task is done by a separate team member and is needed to complete a story .

E.g Story S1 needs -

XML to be created

XML to be loaded

ETL to be created

ETL to be loaded

Config to be updated


Each of these tasks has to be done on Dev , QA & production for it to get completed. Majority of the time , all these cannot be completed in the same sprint for the story to be done .


Need thoughts on how stories should be broken up so that its completed in a sprint and how should environment specific tasks be managed ?




1 answer

0 votes
Cloudites Owner
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 20, 2022

Don't comingle stories with change controls, use different issue types. For example:

S1 - Status: Costomer Signed Off, Issue Type 1 (Many tasks to get to this status)

CC1 - Promote S1 to Pre-Producrion Alpha - Issue Type 2 (Triggered when main S1 issue Status = Customer Signed Off

Compartmentalize stories based on the services layer to optimize well built stories flowing through environment progressions, this will reduce the number of times you have to touch the code for the story, ultimately saving costs.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events