Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
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

How to use boards as a projects (each board is a different project)

We use JIRA projects as products because the defects from the same product can be moved from one project to another. So far, we have been using Sprints to define the projects, but we are looking for a better way to organize our projects. I am looking for best practices and ideas about how to implement the following:

 

  • Jira projects are our products.
  • Inside each product, we will have different boards to define each Project.
  • Inside each board, we will have the normal sprints for each project. But, my main concern is how to configure the board correctly so we only see the tickets for that specific project. I am thinking of using EPIC and adding the EPIC to all the tickets or a custom field with the project name. So I can use the query in the board settings. 

Any feedback or recommendation is welcome.

Thank you

1 answer

1 accepted

1 vote
Answer accepted
Kevin Bui Atlassian Team Mar 05, 2019

But, my main concern is how to configure the board correctly so we only see the tickets for that specific project. I am thinking of using EPIC and adding the EPIC to all the tickets or a custom field with the project name. 

Hi @Georgina Gonzalez - I think what you've described is fine. However, because issues can only belong to one epic, this may cause a problem if you want to use epics the way they were intended (as a way to group issues across multiple sprints).

So instead of using epics to define each project, you could consider instead using labels or components. This frees you up to use epics for their traditional use, if you want to. You can then use JQL to make the board only show which label/component you want to see.

Hope that helps! Perhaps someone who has more experience with managing multiple products in one project will chime in.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

254 views 16 17
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