Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA Best practices (assigning epic to sprint while stories & tasks already assigned to sprint)

Hi All,

Is there is documentation on best practices of JIRA – “Dos and Dont's”? I am facing difficulty of dealing with novices who are using JIRA in wrong way as per their convenience. Hence, I am looking for best practices documented somewhere which I can show to them? The specific best practice I am looking for – should someone assign sprint field to Epic when associated stories, tasks, bugs already assigned sprint fields? As a result, when JIRA calculates points as team commitment at the time of starting sprint, it counts epic estimates as well which doubles or triples the actual team commitment. Also, team’s sprint board starts showing all those epics which in unnecessary. Team does not work on epic directly but stories/tasks etc.

1 comment

Hello,

As you wrote in your message, I consider that only issue with delivery should be assigned to a sprint, so stories, (analysis, technical, ...) tasks, tests, and so on should be assigned to a sprint.

For my part, I am only using Epics as a representation of a large set of functionalities. As I don't really have a Product Owner in my team, I am using Epic to "communicate" with the business : the PO (and the stakeholders) is able to see the progress of the requirements.

Like Vinay_Aggarwal likes this

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

177 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you