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.
Just have a look at the Behaviours Plugin. You can make fields read only using this plugin.
You may like to read the documentation here. Hope this helps.
thanks.
i prefer create screen schemes, but if the issue initator want to edit, it also cann't editable,
the Behaviours Plugin cannot linked the readonly with workflow steps/transition, it only link certain roles.
any ideas?
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"
Great, that works.
thanks you.
How about the inplace-edits?
As I said, don't put them on the "edit" screens.
Jira only allows in-place edit on fields that are on the "edit" screen.
I don't have separate screens for create and edit
It looks like you're new here. Sign in or register to get started.
