Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
Hi, I am tasked with bringing my company's instance of portfolio online and would be grateful for some input/advice. FYI, we are using Kanban methodlogy.
The current JIRA instance has a variety of projects, issues and epics that are not structured in a definative way. I've identified 3 big issues that need to be taken care of.
First, there are a variety of projects that should really be grouped as one project and subdivided with various project components.
Second, we have WAY too many epics (some of which are redundant or should be reclassified as stories). The epics will have to be consolidated, and stories reassigned.
Third, many issues are not associated to anything other than a project. There is no classification such as project-classification, epic-link or labels.
My intended approach is to fix the issue nomenclature/hierarchy in JIRA and then link a board to Portfolio. Is this the only way? Or would I be able to fix alter issue nomenclature/hierarchy directly from Portfolio?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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