when moving an issue the drop down for projects doesn't open

Patrick Aupin September 11, 2024

Hi, I don't know if any of you ever encounter this issue. When moving an issue, in the move screen you have the current project and issue type and there are dropdowns to change them. I have 2 users, when the click the arrow to select a new project (or ticket type), the dropdown doesn't open. One of them is org admin and the other is site admin and I review all the permission. I even logged in as one of them and it worked on my session.

 

They tried with Chrome and Edge and they had the same behavior.

I don't think the issue in in Jira but I can't figure out why only the move screen is affected by that dropdown issue. I assume all the other dropdowns work correctly.

I'm out of ideas.

5 answers

0 votes
Patrick Aupin November 6, 2024

still need a cause, a solution or something on this. thank you

0 votes
Vladimirs Ostaševskis
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 3, 2024

Same problem here, but there is a workaround. You can manually type the project name in the same format as it is shown in field: "Project_Name (KEY)"

0 votes
Viviana Bhandari September 27, 2024

I have the same issue reported to me from 2 users so far,

  • They used to be able to move tickets, first reported issue was back on Sep 11th, 2024
    • As stated in the Patrick Aupin, they do have the option to move, but the dropdown for projects will not even let them open for options
  • We use the same permission scheme for all Engineering projects. 
    • All users can browse, create, edit, etc 
  • I am a Site Admin, I can move tickets

I wonder if there was any recent change from Jira side?

0 votes
Lesley Boyd
Contributor
September 19, 2024

I have a user reporting this as well.  I have them set with the proper project group permissions in both projects.

Has anyone figured out how to solve yet?

0 votes
Katrina Lieber September 11, 2024

Hi Patrick, it's odd that this is occurring - especially since you logged in as those users and were able to perform that activity.

 

The only thing I can think of could potentially be related to the permissions, permission schemes, users, and roles assigned within the projects you're trying to move the issues FROM>TO.  

Although these users are an org admin and a site admin, according to the projects' permission schemes, they may still need to be added to the projects as users and assigned a role that gives them the permissions to move and create issues in both projects. 

 

I would triple check permissions but it is very strange you were able to log in as these users and the project and issue type dropdowns were enabled when trying to move the issue(s) in question. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events