Issue Details (XML | Word | Printable)

Key: JRA-5395
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Jeff Turner [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

'Update Issue Field' post-function value not checked for validity

Created: 30/Nov/04 05:44 PM   Updated: 13/May/05 01:37 AM
Component/s: Workflow
Affects Version/s: 3.0
Fix Version/s: 3.2

Time Tracking:
Original Estimate: 2 hours
Original Estimate - 2 hours
Remaining Estimate: 2 hours
Remaining Estimate - 2 hours
Time Spent: Not Specified
Remaining Estimate - 2 hours

Participants: Jeff Turner [Atlassian] and Mark Chaimungkalanont [Atlassian]
Since last comment: 3 years, 22 weeks ago
Resolution Date: 13/May/05 01:37 AM
Labels:


 Description  « Hide
Many users are shooting themselves in the foot with the 'Update Issue Field' post-function. For instance, they might try to update the 'Resolution' field value to 'Duplicate'. This then breaks JIRA, as the 'resolution' field value actually has to be a foreign key ID into the resolution table.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Mark Chaimungkalanont [Atlassian] added a comment - 13/May/05 01:37 AM
Made the update field post function use the edit template for fields not being plain text. This doesn't prevent the user from stuffing up, but it sure makes it harder! Also updated the error when things do go wrong to be more meaningful.