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

accept button not visible in issue

Erik Lindeman

In my workflow after creating an issue (status new) i must be able to accept it. For this i made a transaction. I got all the permissions necessary but still i cant see the button.

i found a lot about workflow integrity but cant find the integrity checker except the lexorank management integrity checker but that had no problem)

The workflow runs on jira cloud.

Accepted answers

Erik Lindeman

I found the problem.

We imported from a server version with some plug-ins

One of the plugin made it possible to have more/different conditions. In one of the other transitions we had such a condition

for example:

Type: class
Class: com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition
Arguments:

after deleting that one the buttons appeared

All comments

Robin Weiß_y942s1

Hi Erik,

Have you configured some conditions for this transaction?

Erik Lindeman

yes i did but have all the conditions, also tried it without conditions

Robin Weiß_y942s1

My second idea would be a problem with your permission scheme.

If you don't have the "Transition Issues" permission you won't see any transitions.

Probably you already know the "permission helper" found under system witch often helps me to solve these kinds of problems.

Erik Lindeman

got that one too :-)

Even added my name specifically

Erik Lindeman

I found the problem.

We imported from a server version with some plug-ins

One of the plugin made it possible to have more/different conditions. In one of the other transitions we had such a condition

for example:

Type: class
Class: com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition
Arguments:

after deleting that one the buttons appeared

Airbus Driver

To everyone else that is reading this. This is caused due to a limitation of JSU when migrating from server to cloud. Refer to their documentation- JSU: Migrating from Jira Server to Jira Cloud

Refer especially to the following;

Workflows are automatically migrated to Jira Cloud, but the Workflow Configuration will be broken. This is due to how Workflow Conditions/Validators/Post-Functions work on Jira Cloud.

All Conditions/Validators/Post-Functions will need to be recreated

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