How to best structure tagging our issues for Vendor attention and Listing challenges adressed in Ep

[aokeeffe@guidewire.com]

Hi, I am looking for best practice/s advise from Atlassian support community. This is related to the couple of scenarios/use cases I have below that I am trying to figure out for my team as per my manager request;

Use Case 1: I want to re-org the way we tag issues within Jira as below:

a) Initiative issue type > will be our Corporate Strategy Goal/Theme

b) Epic-> Our Team's Sub-Theme tied to Corporate Strategy Theme

c) User Story->requirement/feature tied to delivery of an Epic/Sub-Theme

d) Bugs-> fixes tied to Epic

Firstly - is above a good methodological structure? 

On top of the above, we need to be able to easily identify those (few) stories/bugs that are related to Vendor /will be worked on by Vendor and not us internally. Currently we started to track these as Epics so that Vendor can easily access/view them and see all the items related to their assigned work only, in a single place.

But with our (as above) restructure, the Vendor specific Epic won't work anymore as they may also work towards our Sub-Theme Epics. Since we cannot have 2x epics within a user story, and for very easy downstream reporting later, what is the best approach to tag those stories specific to Vendor dev work? I am thinking to leverage Component for this instead of Epic, but am also wondering does this align with Jira standard methodologies?

Use Case 2: We need to easily track our current department 'challenges'

My manager asked me for easiest/cleanest way to structure Jira so that we can easily track our current department 'challenges'. I know we can use Epic description for challenges addressed within that epic, but I also dont think Description is best when we want to make it a Chart on Dashboard - so not ideal reporting-wise. What are other best/easy methods to list those few challenges taken care of an epic?

Use Case 3: How to best track major process updates within Jira?

So they can be easily exported/seen via dashboard chart and so shared to our leadership?

Any best practice guidance thats easy to follow and easy for reporting would be very appreciated. Happy to jump on call to discuss.

Thank you

[John Funk]

Hi aokeeffe@guidewire.com 

Use Case 1: Yes, that should work well. And I would, indeed, use Components for the Vendors. No issues with using that. 

Use Case 2: What do you mean by Challenges? Are these goals, OKRs, problems? 

Use Case 3: Depends on the format/details of what you are wanting to show. Might be as simple as creating some Filters and adding them to gadgets on a Dashboard.