I've created a Jira Board Company wide and imported project(s) that are team board into the company wide board. However when I create a new Epic, the epic is displayed in the company wide board as "unlabelled-<projectname>-<projectnumber>" and the issues displayed is always 0. Therefore I cannot use the Jira Company wide board to sort through the appropriate issues and its frustrating.
image - shows the unlabelled EPIC with 0 issues, but there is 1 issue, when you select LUI-183 and open it outside into its own board (team managed) it displays.
See image 2.
It looks like the field "Epic Name" has the value unlabelled-LUI-183. I have had issues with this in the past - the Epic Name is not required for Team Managed, but is needed for Company Managed. So you will need to populate that field with the value you want. You (or your jira admin) may need to make this field available for you to use.
@Linda Milne_Know Business_ thanks for responding. it displays directly in that board without any issues, so unsure how do you make it "available to use" is there something specific we would need to enable?
The other issue is even if I manually populate it which would be a pain, I still cannot see how many issues attached, as it says "0", despite there being multiple issues attached to an epic.
If I'm understanding your screen shots - you are using the epics from a team managed project? If you look at the equivalent in a company managed project you have two fields that are used:
And this will translate to:
If you try to view a team managed epic in a company managed context you will not see the Epic Name field populated. You need to make the "Epic Name" field available in your team managed project - your jira admin should be able to help you with this.
@Linda Milne_Know Business_ I went to the issues for the managed project, but we don't have an option for epic name on managed project, theres only a few available fields but its not applicable it seams, that's why in it's own project it uses the same description from epic name and epic name summary. As an admin, it's the same view though. Any ideas around this?
You can migrate between team managed and company managed. Check out:
I suggest if you want to do this you create a test project, that looks like your team managed project, add the same issues with fields as configured in your current project, and try copying it into a test company managed project. Make sure you know what things need to be configured in the new project and how the process will work before you do the move.
yep, I was thinking the same thing to do a test first. it's so annoying though because basically it all works except for the epics, which causes issue for when grooming backlog from the combined company board. it's a shame Jira doesn't fix this issue, but thanks so much for sending this info through.
adding to the great information Linda already gave to help you I found a bug which documents this behaviour:
At the time of writing these lines the bug has 28 votes and 36 watchers.
Please consider adding yourself to the bug mentioned in order to signalize this bug is impacting your work and of importance to your team.
From a personal view: because the bug is not gaining traction as of now I'd also suggest the steps Linda mentioned.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events