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 Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Sunday in Agility

You asked for it, so we delivered: images on issues have arrived

A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...

845 views 3 12
Read article

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