It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to Set some fields as read only after submit an issue?

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.

2 answers

1 accepted

10 votes
Answer accepted

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.

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

Hi. If I remove the fields from "edit" screen they aren't shown in issue view anymore.

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.

Hi Nic, thank you. I got it... I mixed 'em up...

Thank You.. I have separated the screen for edit and create.. then removed unwanted fields from edit screen.. working fine..

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.

This doesn't seem to prevent the user from adding attachments. If Attachments isn't in the Edit screen, they still have other mechanisms to make attachments from the View screen.

Correct. Attachments is not a field, it's a way of attaching files.

Attachment rights are controlled at a project level, by permissions.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

How InVision centralized their tools and scaled their remote team with Atlassian and Slack

Hi Atlassian Community, We recently published a case study that we thought you might be interested in. Learn about how InVision built their fully remote company’s culture using Atlassian and Slack ...

231 views 0 1
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you