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
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
We would like to have agents fill in certain fields when they are transitioning an issue. We have created screens, custom fields and set everything up accordingly.
However, we still notice that agents are also filling in the comments during the transition. Is there a way to remove the comment field from the transition screen? We have set the comments denied permission on the target status, but this doesn't change the screen layout.
The other thing that we would like to do is to make it mandatory to fill in the fields in the screen, without making them required in the issue itself. Is there a way to mark the fields required, only in the screens?
Thanks in advance!
Hi @Paul Wiggers ,
Create a new screen and add all the required fields which should be updated by agents.
Now go to the project required workflow in edit mode, click on the transition and add Field Required Validator and select what all fields are mandatory.
Now add the newly created screen to the workflow transition and publish the workflow (https://confluence.atlassian.com/jirakb/map-a-screen-to-a-workflow-transition-in-jira-720634253.html)
Now when the agent transitions the ticket, a new window with the created screen will pop-up and until agent fills all mandatory fields, it will not transition the ticket.
Hi @Paul Wiggers,
With respect to Comments in your question:
Hope this helps.
If the agents are part of any group/ project role, then remove them from 'Comment Issues' in the permission scheme
-- > Removing user from "Comment Issues" in the permission scheme will remove add comments access for all tickets in the project irrespective of the ticket types.