You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Diego
Welcome to the community.
Option 1) Use jira workflow properties on some statuses (ex: Closed). However, it makes all fields non-editable. It doesn't work on field basis.
Property Key = jira.issue.editable
Property Value = false
Option 2) Remove description field on Edit Screen. Add loop transition that use a screen that includes Description field. Looped transition goes back to where it started. Ex: Open to Open. It doesn't change status but allows you edit the fields. You can even add workflow condition to this transition. Not the best solution but it solves your issue.
Remove the description from the edit screen, and create a manual rule trigger on which you can set status, issue type and groups. Use the Paragraph field which will prompt while running the rule, take the new value of description in it and replace the description value via Edit Field --> Description {{userInputs.description}}
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.
The first method does not meet the usage scenario,thank you very much for your advice
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.