[
https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin....
]
Gary Brown commented on RTGOV-645:
----------------------------------
It may be possible (for now) to just assume that only one situation will be created from
resubmit failure, and if multiple get created, then only the most recent of those will be
candidate for further resubmit.
However that leaves one issue - if there is some way to show this list of child situations
by expanding the root situation, then it means that to do a further resubmit the user
needs to (a) expand the root node, and (b) locate the last situation in the list and
navigate to it. Are you ok with this? Possibly the child situations should be in reverse
order, so most recent first?
Resubmitted message should identify source situation to enable
further failures (situations) to be linked back
--------------------------------------------------------------------------------------------------------------
Key: RTGOV-645
URL:
https://issues.jboss.org/browse/RTGOV-645
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.2.0
When a message, associated with a situation, is resubmitted, ensure that the situation id
is carried in a message header so that it can be included in resulting activity events.
If the resubmitted message results in further situations being created, then these new
situations should include the reference back to the originating situation id.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)