As a Jira administrator, our process requirement is below:
Jira user add an issue, then following process step should'nt change any the original fields which the first user filled even the issue iniator?
thanks in advance.
I wouldn't worry about the behaviours plugin, you can do it without that
Look at the "screen schemes" and set up a "create" screen which contains all the fields, and then have the "edit" screen exclude them. People won't be able to change the original fields.
That suggests that you are using the same screen for edit and view. Separate them out. Same for the previous comment - you need separate screens for create and edit. Copy the existing one, then change the issue type screen scheme so it uses the new screen for edit and change that copy.
Your original question said that no-one should be able to edit the fields after initial creation.
But that's still possible with screen schemes, as long as you're happy with a slightly ugly hack.
Basically, you move "edit" into the workflow. Do what I said already, but then add a third screen to the system, one that includes all the fields you want to edit (you could just use the "create" screen for this of course). Then, go into the workflow, and on each step, add a transtion that loops back to the same step. Use the new screen for the transition. Finally, put "conditions" on the transition - the one you need to begin with is "only the reporter of the issue can do this transition"
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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