Can an issue have its own sub-workflow for its child issues?

[Konrad]

I have been looking for possible solution but couldn't find anything, so I apologise if I am asking about something obvious. 

I am working on a system that is comprised of issues (epics) and child issues (stories) in the Jira Work Managemnt context.

For example purposes only, the epic issues transition between statuses ‘To Do’ <-> ‘Open’ <-> ‘Closed’, however within each epic issue I would like to have stories (child issues) that would transition between another set of statuses (sub-workflow) such as: ‘Application’ <-> ‘Screening’ <-> ‘Testing’ <-> ‘Resolved’, can this be done?

Basic solution is to have project with issues (epics) and from within each issue there is web-link to another project (with sub-workflow) and stories, however that is very cumbersome. Could I contain this within one project?

Perhaps I am missing something obvious, perhaps there is another way of designing it using existing Jira programming blocks?

[Shawn Doyle - ReleaseTEAM · Accepted solution]

Short answer: Yes each issue type can have it's own workflow. There is no need to nest projects to get different workflows.

I am moving your question to the Jira forums, you may get more in-depth answers there.

[Konrad]

Thank you Shawn, hopefully someone will provide more in depth answer.

[Hans Polder _Devoteam_]

@Konrad ,

The answer depends on what type of projects you are using. You already mentioned 'Jira Work Management', which is clear. But, do you use team-managed projects or company-managed projects? You can see this in the left bottom corner of your selected project.

Also, can you please go to the Project Settings and share with me a screenshot of your current Workflow setup? You can open the Workflow-menu item on the left and show the details on the right. Feel free to anonymize anything that shouldn't be on the internet :)