I'd like to show a specific screen that contains a select set of fields to users only when moving specifically from one project to another.
The larger story:
I have a team (A) who uses a project to track their work. When they complete certain kinds of work, it's handed off to another team (B). This team is a non-technical team and resisted incorporating JIRA into their work process, so team A created a second project (Z) and used a transition to clone Project A issues of this specific type into Project Z. This allowed team A to close things on their board as well as (manually) track work they'd given to team B.
Team B liked the board that was created and has since started using JIRA to manage their work. Since they do other work than what team A gives them, they created Project B which has workflows more aligned with their tasks and various issuetypes. Now they want to move the contents of the view-only Project Z into Project B.
What I'd like to do is create a transition in the Project A workflow that, when triggered, creates an identical ticket in Project B (that's the easy part) but prompts the user with a screen of selected fields from Project B (those which were previously the fields of Project Z).
I feel like I should be able to created an issuetype screen scheme which would contain a screen of select fields that could be attached to the either the create or edit screen, but the catch is I want a screen that only shows up during this move–the normal create and edit screens should remain in tact when creating or editing a Project B issue. This is the part where I'm getting stuck and would appreciate advice.
I'm afraid that's not what "move" is for. All it does is the minimum to validate the data in the original issue will be valid in the configuration of the new project and issue type, and ask you to update any fields that need to change. There's no hooks for new screens or processes, it's just a simple move.
All I can think of doing is writing an add-on to implement your own move process, and disabling the built in one (removing "move permission" from everyone in project A)
Makes sense. I assume about the same should be expected when cloning an issue?
I guess I was assuming that:
then a subset of fields could work as I'm thinking. I guess there's a bit of a leap there.
If this isn't possible, my only option then is to have all fields made available to the person moving the issue from Project A to Project B, correct?
Cloning is easier - the project and issue type aren't changing, so there's no structural changes. But that does mean there's no need for any screens or customisation either. There are a few add-ons that try to cater for more advanced cloning rules - "clone and move, clone but drop these three fields, clone but reassign" etc. (Those are examples of rules, not add-ons. Although there is a clone and move add-on which can do a lot of sneaky stuff)
I think, without your own add-ons for move, yes you have outlined the only option.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs