How do I control issue type hierarchy within Job Work Management?

[Callum Wells]

In Jira Software you can customize the hierarchy of issue types although the feature doesn't seem to be available in Job Work Management.

Essentially I want to able to create the following:

Epic

- Story

-- Task

--- Sub Task

This article offers guidance of setting it up for Jira Software but how do i do it on job work management.

Configuring initiatives and other hierarchy levels | Atlassian Support | Atlassian Documentation

Also in the timeline view when adding a task under an epic it only allows me to create a sub task but in Jira software it only allows me to create a new story/task etc

Cheers,

[Nic Brough -Adaptavist- · Accepted solution]

I don't think REST exposes that information, because it's not a simple direct relationship.

Given a project, you'd need to read the list of people and groups in roles, then expand the groups out to people, then read the permission scheme to work out if your user matches the rules for access. You also need to think about what "access" means (just "I can see issue", or something else?), and how to handle the dynamic roles like assignee and reporter etc.

However, REST respects the permissions of the users internally, so if your rule is "person must have browse rights", then your normal user trying to use REST will only see the projects that they see when they use the UI.