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; } } }

Create issue transition not working

Brooke Musat

I am having an issue with the "Create a new issue" post function.

Despite several attempts, I can not get the new issue to fire.

It is important to note:

1. The post function is on the close transition (anything going into close)

2. The original issue is a sub task and I am trying to create a new task (not a sub-task) in the same parent type but a different issue type

3. There aren't really any conditions to this create-issue-transition, but rather it should happen every time the sub task moves into "close"

4. Also, after editing the workflow, I did published it.

See screenshots for more detail.

Accepted answers

All comments

Jonny Adams

@Brooke Musat Does the "Run as" user have the create issue permission in the project?

Does your project include the Task issue type that you are trying to create? Can you manually create that same issue type?

Brooke Musat

Jonny, thanks for your reply.

On this: Does the "Run as" user have the create issue permission in the project?

I am not sure where to check for this, where would I look? Project >>permissions? I will say the project doesn't have any specific restrictions.....anyone can create any issue within this project.

Does your project include the Task issue type that you are trying to create? Can you manually create that same issue type? Yes to both of these questions.

Jonny Adams

Right. Project>Permissions>Create issue.

Something else you may want to check, do you have required fields in the issue type you are creating? I believe the issue won't be created if those fields are not filled.

Brooke Musat

Yeah I thought of that, I do have required fields and I am coping them over from the subtask. They are called out in that second screen shot (due date and account owner).

I also checked the permissions for the project (just now) and that was a dead end too....all JIRA users under our instance can close and create issues.

Any other ideas?

For some reason, it feels like the issue may have something to do with it going from a subtask to a task seems. This is just a hunch, but I am honestly not sure what else to try.

Welcome!

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

Quick Links

Find more posts tagged with

jira

transition