[overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back

[Michael Ilger (JIRA)]

    [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051273#comment-13051273 ] 

Michael Ilger commented on RTGOV-645:
-------------------------------------

Hi Gary,

Regarding your questions:
Represent situations in a tree representing the resubmission failures: This could lead to usability problems, as the user has to do a lot of extra navigation to get the details of all situations. Additionally there are also bulk actions and filters to keep in mind.

The root node shows the number of resubmits so far (this is equal to the number of child nodes): Showing the total of child nodes sounds like a reasonable approach to just give the user a feeling of the overall amount of data connected.

Only the newest situation in a tree is allowed to be resubmitted: From our point of view the newest situation can always be retried (also multiple times, given that it stays the newest situation)

[..]Either the tree is fully shown or hidden: This really depends on the definition of leaf node, and what we expect the tree to look like. Our assumption is that all resubmissions are immediate children of the original message, which gives us a tree of depth 1 with a lot of leaves.


> 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)