Best Practices: Strategies for Defining your JIRA Projects

We are in progress with a larger rollout of Jira, where we have many applications. It was originally intended that each application should have its own container, but later this year we will launch a larger IT system, consisting of four major applications. We are facing a challenge about setting up a change process in Jira. The first thought was to have a container for all applications and a component specified affected applications. But it presents some challenges, as each application has different information needs. We thought to create a Core container, where all changes are created and then clone the case to effected applications. I'm looking for someone who has some experience in the area around what works and what does not. I want to make it simple and easy to maintain - even in relation to releases.

0 answers

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,968 views 12 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot