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

Your Points Tracker
  • 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
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?
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

What is the best practice for including external project work in your sprint?



I would like to capture the effort involved in external projects and include that effort in my sprint estimation (note I have team members working on both internal project work and external). One way is to clone a ticket from the other project and include it my project and sprint. Wondering if this is the best practice?


Thank you

2 answers

2 accepted

1 vote
Answer accepted
Mirek Community Leader May 09, 2021

Hi @Mk j , 

Are you having "projects" on the same instance, or by saying internal and external those are separate? 

If those are on the same instance I guess you can simply include issues from both projects by modifying board filter.. 

Boards is a layer on top of issues so you can view them from different projects not only one. 

Same instance. Thank you for your reply. this was helpfull

1 vote
Answer accepted

It's not far off.

The easiest, and probably best, way to do this is include the "external" issues in your board, so there's no duplication, but if you can't do that (because it would mess with other people's numbers), then your idea of Clone and include is probably the next best option.

One of the projects I'm on at the moment has a Scrum board that does exactly this - the filter for the board is "Project = XYZ or label = 'xyz-include'"  (Obviously, not quite that, but the point here is the board uses a label to draw in the odd issue that the team doesn't have in the XYZ project directly)

Thank you for your reply. this was helpfull

Suggest an answer

Log in or Sign up to answer

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