|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Vineet Reynolds <vpereira@redhat.com> made a comment on bug 978925
Description of problem:
When deleting entities like Performances from the Administration site, the entities are not deleted at all and reappear after deletion or failures are encountered during deletion.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Click the Performance entry in the side-bar.
2. Select an existing Performance in the list of Performances to view the performance.
3. Click the Edit button to modify the Performance.
4. Click the Delete button to delete the Performance.
Actual results:
An error message stating that a constraint violation error has occurred, is displayed upon deletion of the Performance.
If Forge 1.3.1 or earlier was used to generate the Administration site, the deleted performance will reappear in the list of performances.
Expected results:
The Performance should be deleted.
Additional info:
This was fixed upstream in the TicketMonster Git patch (
JDF-389). The issue involving re-appearing of deleted entities was fixed inFORGE-916(released in Forge 1.3.2).