Using Parent from Product Discovery Projects

[Kayla Zimmermann]

We are using Objectives (issue type) from the Product Discovery Projects as the highest hierarchy level, however it appears we are not able to link the objectives as Parents. We'd like to use these to create Filters for Jira Plans. Looking at the issue Hierarchy- Epic appears to be the highest level supported. Is there a different way to easily build a Plan with multiple epics and Projects- and organize by Epic?

[Walter Buggenhout]

Hi @Kayla Zimmermann and welcome to the Community,

While I have not been able to simulate this, I know Jira Product Discovery is under the hood based on team managed projects. The elements of team managed projects have been restricted to that single project and I have an educated guess that these are not available outside of this single project, and possibly not available to extend the hierarchy.

If I am mistaken, you should be able to add a level to the issue hierarchy and associate the objectives issue type with that new hierarchy level.

Hope this helps!

[Hannes Obweger - JXL for Jira]

Hi @Kayla Zimmermann

welcome to the community!

I believe that @Walter Buggenhout is right on the limitations of JPD projects. One thing to consider is that you can always use issue links to represent your hierarchy. The problem is that Jira won't really understand issue links as parent/child relationships and therefore not provide a lot of relevant features.

This being said, if you're open to solutions from the Atlassian Marketplace, you'll find apps there that can do that. Just as an example, my team and I work on an app that could easily represent the hierarchy you are looking for: JXL for Jira.

This is how it looks in action:

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 range 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 task/sub-task), and/or based on issue links. In the above clip, the various epics relate to the JPD issues through issue links.

Any questions just let me know,

Best,

Hannes

[Sergey Shoshin]

@Hello, @Hannes Obweger - JXL for Jira , Could you please share the hierarchy configuration? Trying to understand how you build a structure based on delivery tickets.

There is no "Link" or "Parent-Child" or something in the settings

[Sergey Shoshin]

Ok, @Hannes Obweger - JXL for Jira I found this setting working:

So, this linkage can be used anywhere else (except any of Atlassian Hierarchy, for sure) in all possible plugins.

The only problem -> It is required to find out all possible children first from all projects, so it is also required to apply Advanced Search plugins with Parent-Child search capabilities

[Hannes Obweger - JXL for Jira]

Hi @Sergey Shoshin

glad you got this to work! For future reference, you can find the relevant documentation here.

so it is also required to apply Advanced Search plugins with Parent-Child search capabilities

Not necessarily. Another option would be to use a broader JQL statement in your sheet's sheet scope - i.e. pulling all potential children - and then use JXL's filtering capabilities to hide those that aren't actually relevant. (JXL can download hundreds if not thousands of issues very fast, so unless you're dealing with very large amounts of issues, this shouldn't cause any problems.) Specifically, you can use JXL's level filtering settings to hide all child issues without parents.

If this needs further sparring, please be so kind and reach out to us at https://support.jxl.app so we can take a closer look at it - thanks!

Best,

Hannes