INITIATIVE as highest work item parent in Jira Standard subscription

Question

I am looking for the possibility of adding INITIATIVE as the highest level parent, so eventually my hierarchical structure will look like INITIATIVE > EPIC > User Story > Sub-Task & should be able to link TASK & BUG as separate work items.

I am on Jira Standard subscription.

Hannes Obweger - JXL for Jira · Answer

Hi @Mayuresh Athalekar

if I may provide another Marketplace recommendation, this would be easy to do using the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies. These issue hierarchies can be based on Jira's built-in parent/child relationships (like epic/story, or story/subtask) and/or issue links of configurable issue link types. This means that you can simply create a new issue type (like "Initiative"), and create or chose a fitting issue link type (like "is parent of"/"is child of"), and model a hierarchy like this in just a couple of clicks:

You can also combine such a hierarchy with JXL's other advanced features, such as issue grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know,

Best,

Hannes

Mark Segall · Answer

I'm not as familiar with Structure, but it relies upon issue links to create a logical hierarchy.  I've seen environments where they create a new link type with options of "Is Parent Of", "Is Child Of".  Once you set those links, Structure can help dynamically generate the hierarchy visually.  I know that the Structure team has historically been very active in these community threads so hopefully this catches their eye and they can provide further assistance if needed.

Mayuresh Athalekar_yfnud4 · Answer

Yes. I did that in my one of test project. However it is not reflecting in the way i want to see in Jira roadmap or even at other places where the hierarchy should reflect for various use cases. As @Mark Segall mentioned, Jira Standard has this limitation and requires external app which perhaps the needful information will be available by experts in this thread soon !