I want to give my customers the ability to upload Issues in a Global Project without letting them know which project it affects for real.
For example, I may have a Project for API Development and another for Web UI Development, and the customer doesn't know where the requested requirement should go.
I created a new kanban project that only has Epics as issue types, but I cannot work with epics as stories moving them inside the Kanban board.
So I was wondering if there is already something for this.
The main advantage would be to keep updated my customers on what we are working on, and have every dependency updated in Portfolio
The first thing I was thinking about is using one single project but splitting it up into several sub-projects using Components.
That way both your customers and teams are working on the same project but you'll still be able to split the issues between the different teams/components of your application.
Hope this helps,
Hi Maarten, thanks for the reply!
I've never used components before, I'm going to check it out now.
However I have all my teams already working on their projects so I'll prefer not affecting the current projects we have and create a new one for my customers if possible.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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