Issue Details (XML | Word | Printable)

Key: JRA-4972
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Jeff Turner [Atlassian]
Votes: 15
Watchers: 7
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

Force users to add comments on transitions

Created: 19/Oct/04 01:52 AM   Updated: 23/Jan/08 12:06 AM
Component/s: Workflow
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: David Donn, Jeff Turner [Atlassian], John M. Black, Timothy Hallbeck and Tom Miller
Since last comment: 45 weeks, 1 day ago
Labels:


 Description  « Hide
It would be nice to have a workflow 'validator' that ensures that transitions are not made with an empty comment.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Timothy Hallbeck added a comment - 24/Nov/04 02:59 PM
I would like to just turn on Required for the comment field, but it's not listed by ViewIssueFields.jspa. Workaround is to add a custom field called CommentRequired and set it to Required.

John M. Black added a comment - 16/Nov/07 01:11 PM
Please make sure this is not implemented globally. There are many times when I, as a user, know that there are already sufficient comments or other content in the ticket, and there's no reason to enter anything. Forcing me to enter something would be very inconvenient.

Also since we use the SVN plugin, we don't even require comments on Fix, because we can always view Subversion Commits for that.

If there's a way to give admins the option to do this in workflow that's fine, but don't make it on by default.


Tom Miller added a comment - 07/Dec/07 09:15 AM
I think there needs to be a second work flow screen (actually a handful but I digress) Workflow and Workflow Required Comment so you can attach them to specific transitions as needed.

David Donn added a comment - 23/Jan/08 12:06 AM - edited
One workaround is to implement your own comment validator. This worked for me, though a "proper" solution for comments is still desirable as my solution lacks an user feedback in the initial form about when a comment is required or not.

e.g.
public class CommentRequiredValidator implements Validator {

public final void validate(Map transientVars, Map args, PropertySet ps) throws InvalidInputException,
WorkflowException {
if (transientVars.get("comment") == null) { throw new InvalidInputException("Comment is required"); }
}

}