nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Workflows/Schemes Frustrations - Seeking Help

unknown

I am a relatively new Project Admin, learning everything by trial and error. I've searched through the documentation, but can't figure this out.

I created a project, added a workflow, screens with custom fields, schemes, etc. Only tasks and sub-tasks were used. Everything works great. Issues created, transition validators working properly. Everyone's happy.

Then my boss requested a change. The sub-task should only be used under particular conditions and should bring up additional custom fields. I removed all reference to sub-type from the original scheme, and created a second workflow for the sub-task. But then as I was working through the documentation, I noticed a statement that said "there can be only one associate for an issue operation per Screen Scheme".

I thought that meant I couldn't have create/edit/view on the sub-task unless that was under a different scheme. Just to keep everything clean, I made a new workflow scheme and a screen scheme for the sub-task. However, when I try to add the issue type of sub-task to the scheme, it tells me "You must select at least one standard issue-type for your scheme" and won't let me save the issue type scheme.

I can't figure out what I'm doing wrong or how to get this to work properly. Any help would be sincerely appreciated.

My test environment is Jira 7.8.1, server-based.

Accepted answers

Alexey Matveev

Hello,

In the issue type scheme you should add a standard issue type. Just add it.

All comments

Alexey Matveev

Hello,

In the issue type scheme you should add a standard issue type. Just add it.

unknown

Thank you, Alexey. I understand that it wanted an issue type (and I thought sub-task WAS a standard issue type).

I've since ascertained that the issue type scheme corresponds to the entire project, which implies that I can have different screen schemes associated to either the task or sub-task. However, the screen scheme seems to only allow one or the other, not one for each issue type.

The workflow seems to be fine; it allows the sub-task workflow for only the sub-task screen. Trying to figure this out through trial and error is a frustrating process, especially when most "beginner" documentation is geared towards agile projects, not business projects.

I'll keep plugging away, but if anyone has gone through this successfully, I would love any tips!

Alexey Matveev

You should first create two screen schemes: one for standard issue types and one for subtasks. Then you should associate each screen scheme with an issue type in the issue type screen scheme and then associate the issue type screen scheme to your project.

unknown

I discovered that although the association of the issue type screen scheme appeared to be an either/or scenario, it was actually accepting both schemes. My frustration was that I was following directions meticulously, but it appeared that only one scheme was active when both were.

Thank you again Alexey. I will be glad when we upgrade to the latest version of Jira.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server