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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Portfolio for JIRA - Epic with various projects child issues

Hi guys,

 

The use case is pretty simple but I don't understand why it's not working:

I have 2 projects ES and OBT. I have 2 boards for my 2 teams.

- 1 board includes the entire ES project + issues from OBT project that have a specific component (let's call it X)

- 1 board includes the entire OBT project - issues from OBT project that have the X component

 

Therefore, those 2 boards are pretty exclusive. No issue is present on both, i've double checked it.

 

Here's the thing: When I import the scope, I choose the 2 boards and, by default, issues from the OBT project with the component X are unchecked. Not a big deal since I can select all. But, if I add a new one to the epic, it won't appear in my plan, which is very annoying. It means I would have to redo an import every time one of the team is adding an issue like this one.

Screen Shot 2018-08-14 at 1.32.18 PM.pngDo you have any idea on this one? Should we migrate those issues to the same project (ES)? The reason we kept like this is that the component fixversion would coexist on both projects and that's not ideal.

 

Thanks

Julien

1 answer

0 votes

I understand how the projects are configured. While replicating the behavior, I'm not entirely clear on what you meant by the following line. 

But, if I add a new one to the epic, it won't appear in my plan

 

Could you clarify what did you add to the epic?

Hi Chung,

Thanks for your message. What I meant is that if, after the creation of my plan, I create an user story under an epic which is from a different project, it won’t be part of my plan’s scope unless I redo the import of all the issues.

thanks 

julien

Hey Julien, 

Any issues outside of the 'Issue sources' will not show up in the plan, even if it is linked to an Epic that exists in the plan. 

The problem is those issues are in the results of the board filter.

 

Here are my 2 boards respective filter:

TEAM ES:

project = ES OR project in (OBT) AND component in ("Buying Flow", Frontend) ORDER BY Rank A

TEAM OBT:

project = OBT AND (component is EMPTY OR component not in ("Buying flow", Frontend)) ORDER BY Rank ASC

 

the issue in the screenshot does have the component "Buying Flow", does appear in Team ES board but it's not part of the scope unless I redo an import of issue sources by selecting all the issues

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....

121 views 2 6
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