Advanced Roadmap hierarchy

[PCAFrance]

Hi,

I do not succeed in showing tasks (and sub-tasks) under story. They are at the same hierarchy level.

On Issue type hierarchy page, i have:

If add Story as Jira Issue Types, I can not change the hierarchy level as explained : https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/

The drag and drop does not work in order to change the hierarchy level.

What do you think about it ?

Best

[Nic Brough -Adaptavist- · Accepted solution]

I am sorry that the answer you got form @Diogo Teles  before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software.

Plain Jira's hierarchy is simply 

standard issue type

sub-task types

Jira Software adds Epic as a layer above, and Advanced Roadmaps allows you to have more than one issue type at the Epic level, and create layers of other types above Epic.

But the core standard/sub-task hierarchy is immutable, you can not change it.  You need to define an issue type as a standard type or a sub-task type, and you can't change a type between those layers.

[Diogo Teles]

Hi @Nic Brough -Adaptavist- 

I must contest this. I'm sorry. I spent a lot of time on those answers. I have generated screenshots on my instance. I used Jiras's issue hierarchy config to create example levels to illustrate the solution. If you look at the examples used in those screenshots, you will find it very hard to generate them with an AI. You will also notice that one of them was edited to highlight an option. If you wish, I will schedule a video meeting and replicate the process while sharing the screen to our Jira instance where those screenshots were generated. My contact if shared on my profile.

Additionally, as for the text itself, I wrote from a personal case, and it is a shame you removed that answer because @PCAFrance  may be legitimately struggling with the same issue. We had users asking about subtasks not showing under story-level issue types. The reason, in the end, was that they were using a board filter as an issue source which, in its query, filtered out subtasks. 

You are also not addressing the original question's potential issue of confusing "tasks" with "sub-tasks", which may have been the root cause for some concerns.

I understand and agree with the need to screen for AI-generated content. I do not know what kind of AI is used to determine if a post was AI-written, but its use should be reviewed.

The only AI assist I use in my posts is Grammarly, which helps me with grammar articulation and tone. If that will make us get in trouble here in the future, then I advise setting up some specific community guidelines. If they already exist and I missed them, please point me in their direction.

[Nic Brough -Adaptavist-]

I am sorry, but that is not correct. 

All three extensions I use in my browser said your text has a 95%+ chance of being written by an AI, and ChatGPT generated pretty much the same text when I asked it the question. 

It was also factually incorrect, and did not answer the question.  I know you made some effort in adding the screenshots to it, but the text of the original was misleading, and did not explain the answer.