It is very fluid at the moment, as we do not have someone driving the implementation. The global instance of JIRA is ~4 months old. At one point we had a JIRA expert -> they left -> now I see a wide array of interpretations around the company (20K employees). I went down the route of creating a project per initiative for my business unit. Another business unit created a single project to house all their initiatives, even though they are not related. I am trying to figure out the best practice to determine potential long term impact.
If you create a project for each initiative, my guess is that you get a clear view around the data. If you do not go this direction, you have a single project that accumulates massive amounts of artifacts over time and could result in convolution of data sets.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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!
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