It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Hi folks,
I am putting a property to my workflow transition, but an issue still remains editable.
I tried those ones:
When I'm exporting a workflow as an xml file, I can see the following:
<action id="61" name="My transition">
<meta name="jira.description"></meta>
<meta name="jira.permission.edit">denied</meta>
<meta name="jira.fieldscreen.id"></meta>
or
<action id="61" name="My transition">
<meta name="jira.description"></meta>
<meta name="jira.fieldscreen.id"></meta>
<meta name="jiia.issue.editable">false</meta>
Any ideas?
I believe that property only applies to statuses, not transitions. While an issue is in a status flagged as not being editable, the issue will not be editable.
That's not the point.
In the next status the issue still remains editable, as I mentioned above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Because you set it on the transition. You have to set it on the status explicitly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also be careful on your spelling I can see in your excerpts that you have JIRA spelt as jiia.
jiia.issue.editable=false
when it should be
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Phill, you're right.
But after correcting the typo the issue is still uneditable(
I even tried to add a custom database table prefix, but it also didn't help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As Jeremy already said, jira.issue.editable is a property of statuses, not transitions.
Add the property to the status instead of the transition and it should work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Where should the issue be not editable? During the transition - then remove the screen used in that transition, or in a status - then add that property to the status as Jeremy mentioned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Gyus,
I got it. Now I feel stupid)
Thank you so much for help! Those buttons look alike)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What if you want the screen to be there AND the issue (or a specific field) to be uneditable?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello there,
nearly the same Problem here..
i put the property to one Step of a certain Workflow.
Issues in this Step are still editable.
Any ideas why?
image2016-2-18 10:24:45.png
Regards,
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Workflow wasn't published .. now it works.. thank you very much!
Feeling like a bloody beginner again
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.