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

I've mooved a task to another Project with the same tasktype. The other project have the same workflow. But now the moved Task provide no buttons to trigger the workflow. What's wrong?

Elmar Hirt

Accepted answers

All comments

Jobin Kuruvilla [Adaptavist]

Maybe it is using a different permission scheme? Or has different users in the project roles?

Your workflow might be using project roles or permissions in workflow conditions.

unknown

Good call Jobin!

Jobin Kuruvilla [Adaptavist]

smile

MattS

I do wish there was a way to show admins why a transition is not shown in an issue. A "where's my button?" feature

Ignacio Pulgar

Your user is likely to lack the 'Transition Issues' permission on the second project.

Check that your user has been added to a project role which is being granted such a permission in the underlying Permission Scheme.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-core