Hello all,
I know there is a way to move issues between projects, but is there a way to move them easier with a single button for example?
I think you're questioning the reasoning behind "move issue" needing to go through asking you a whole pile of questions.
Moving an issue is changing its fundamental structure. The unique key may change, the fields, the worklows, how it works in front of the users.
It simply cannot be a simple process of just moving it. An analogy I've knicked from someone years ago.
Issue = get a person (reporter) from London to Liverpool. Issue type = Car, assignee = driver.
Start work on the issue, get to a service station on the M5 or M6 take a break, and change driver. Fine, you reasssign it. But would you then change the car to a helicopter as well? Yes, you might, but that's a massive structural change to the issue. The assignee might not have the skills, so no longer be a vallid assignee. The fields "wheels", "type of fuel", and so-on might have to change (heck, "electricity" is not even a valid type of fuel for a helicopter, so that's a big structural change), and, and, and...
Isn't the Move command a single button? I am not sure what would be easier.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I meant that I have to click next and confirm a couple times. I meant a button that I only have to press once to go from project A to project B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes I see. The issue with moving between projects is that things don't always match up and the program is unable or should we say unwilling to guess. These decisions are left to the user (human) to make the decisions.
so to answer your question more directly- No there is not a one button solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's still a valid concern, especially since we've recently updated our Jira setup to separate the Project Queue from Operational Delivery Project. As a result, transferring an issue to another project has become more complex.
To streamline this process, we may need a dedicated Move button that allows seamless issue migration to a new project with a similar structure but a different number. This would help maintain consistency while reducing the extra steps required for manual transfers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.