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

Restrict user to move issue into a project

Rahul Aich [Nagra]

I want a user to be able to create issue in my project but not allow him to move an issue from another project to my project.

How is this possible.?

I know that Move operation also depends on create issue permission so i cant achieve this out of box.

Rahul

Accepted answers

Nic Brough -Adaptavist-

That's a really good one. Although I suspect the use-case is pretty much "ask your users to stop being a bit silly", there's actually no way to do this off-the-shelf, and I can't think of a way to block it without code.

The problem is that I can't think of any way to block the move - it doesn't actually execute the "create" transition, so you can't plumb any code into transition functions to block it. That means you're going to have to dive into the core code in JIRA to change the permission checks that "move" does. Or disable "move" and write your own addon to do it

All comments

satyanarayana v

Hi Rahul,

Move operation doesnt necessarily depend on Create issue.

The way I used Move Issues permission is I created a Role called "Multiple Leads" and assign the users to Leads so only Leads can move issues not all the users but any user can create issues in my project.

Udo Brand

Yes, it also depends on create issue permission.

In order to move an issue from project A to project B the user needs move issue permission in project A (source project) and create issue permission in project B (target project).

So the user must not have move issue permission in all other projects than your target project. But this could be hard (or impossible, depending on the requirements in those other projects) to set up.

Nic Brough -Adaptavist-

Daniel Bower

I'd also like this functionality. It seems there isn't very much control around moving issues. It would nice to have transition-like controls in place. It's wishful thinking to be able to ask users to not be "silly". I'd like to be able to use a post-function that says "If custom field X = Value A, then do not allow Move". In our use case, customer-reported issues should always remain in our maintenance Project, but we'd still like the ability to move internally-reported issues out of the Project, as well as internally moving issues within the project.

Nic Brough -Adaptavist-

Why would you want to stop someone moving an issue into a project, when they have the right to create in there? They'll just get annoyed and either not bother to do anything, or they create a copy, probably missing information including where it came from. (That's the "silly" bit, the "prevent user from moving an issue out of a project" you describe is perfectly sensible. But sadly, not implementable in JIRA)

Daniel Bower

In this case, there's a maintenance project and a new development project. Users should be able to create in the new dev project and move feature requests into it - but not customer issues. It's a training issue, but if we could put a control in place it would make things that much easier.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration