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

Best Practices: Strategies for Defining your JIRA Projects

62 comments

Matthew Wong Atlassian Team Sep 27, 2019

@Foubs - You would simply create projects according to business unit.

Foubs I'm New Here Sep 27, 2019

Thanks but then where do you create your business unit ? is it only as a category or tag, not as a sort of container ?

Matthew Wong Atlassian Team Sep 27, 2019

@Foubs You don't create business units anywhere (although you could use user groups for that). The projects should mirror your business units themselves, which is the intent of the article. Hope that clarifies.

I thought I posted this comment but now I do not see it, hopefully this isn't a dup but it will be a shorter comment now :-P.  Our PM and mgmt team want us to move to separate projects by high level area.  Right now we have one very large project.  The ask is to move to say 4 projects so the backlogs are separate, ranking within the project areas are separate, progress can be tracked by area, etc.  Each of these project areas will have more than one team.  Deliveries and releases, however, can include work from any one or more of the areas.  This means we will need to keep the releases in each of the projects in 'synch' and release them each when one release is delivered.  Components can be customized by project in this setup but there may be a problem if anything moves between projects (the component value may need to be adjusted or added if it is in the "from" project but doesn't existing in the "To" project.  

Is anyone following a like model?  Is there a way to keep releases in synch across projects (or an add-on that helps)?  Any other gotchas with this type of setup?

Matthew Wong Atlassian Team Dec 18, 2019

@Lorraine_Gorman  - thanks for touching base. There are definitely gotchas with particular project setups. As you called out, releases will be managed separately per project if you break out your streams that way. It can be a bit of a pain or manual for any particular scenario.

You might consider creating multiple boards for the same project and categorize work according to a field like component. That way everything exists within the same project, but you have separate backlogs but you can manage releases together. The drawback here is that you'd have to make sure to select a component for every issue you create, but a required field could take care of that easily. It'll also eliminate you having to worry about migrating issues between projects.

Thank you for this discussion regarding release management with jira.

Perhaps a project for "Company 123".

Then an epic for "Company Website" and another epic for "Top Secret IOS app", etc.

anyone an internal IT dept here?  we are aligned by HR function (in jira) which is making collaborating very difficult.  brainstorming new ways to organize projects with the following requirements:

  • shared services (cyber security, training and communications, infrastructure)
  • Intact PMO looking to capture traditional metrics (start and end etc)

cc @Matthew Wong 

Is it generally a bad idea to have a "front-end board" and a "back-end board"?

@Kenny Peere No it is not bad. However, it is important to note that you should make it front-end xxx project and back-end xxx project... then create a board where you can have both the front-end xxx and back-end xxx project on the same board. That way, you can co-ordinate sprints for xxx project.

You can then create another front-end yyy project and back-end project yyy. Depending on your need.
However, you can also create a single project, create an epic with user stories and let the front-end and back-end devs create subtasks related to a user story in an epic, OR, they create tasks related to an epic, under the epic.
And if the task is not related, they just create tasks but not under any epic.

Comment

Log in or Sign up to comment
Community showcase
Published in Jira

Keep your team in the loop with Team @mentions in Jira Software!

Hi everyone! My name is Jenny, a Product Manager at Atlassian. After launching Team @mentions in Confluence, we heard a lot of positive feedback from customers that they love how easy it is to @men...

265 views 4 12
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