April 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-652) Sortable columns on Resubmit Failures tab

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-652?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-652: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/287 > Sortable columns on Resubmit Failures tab > ----------------------------------------- > > Key: RTGOV-652 > URL: https://issues.jboss.org/browse/RTGOV-652 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > The columns on the "Resubmit Failures" tab should be sortable, as they are on the "Situations" page. > The default sort order should be the same as the default sort order on the "Situations" page (currently descending by Timestamp). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-652) Sortable columns on Resubmit Failures tab

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-652?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-652: ----------------------------- Fix Version/s: 2.1.0.Beta2 > Sortable columns on Resubmit Failures tab > ----------------------------------------- > > Key: RTGOV-652 > URL: https://issues.jboss.org/browse/RTGOV-652 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > The columns on the "Resubmit Failures" tab should be sortable, as they are on the "Situations" page. > The default sort order should be the same as the default sort order on the "Situations" page (currently descending by Timestamp). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-651) Add a Refresh button to Resubmit Failures tab

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-651?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-651: ----------------------------- Fix Version/s: 2.1.0.Beta2 > Add a Refresh button to Resubmit Failures tab > --------------------------------------------- > > Key: RTGOV-651 > URL: https://issues.jboss.org/browse/RTGOV-651 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Beta2 > > > A Refresh button is missing on the "Resubmit Failures" tab, as it is available on the "Situations" page. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-651) Add a Refresh button to Resubmit Failures tab

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-651?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-651: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/287 > Add a Refresh button to Resubmit Failures tab > --------------------------------------------- > > Key: RTGOV-651 > URL: https://issues.jboss.org/browse/RTGOV-651 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Beta2 > > > A Refresh button is missing on the "Resubmit Failures" tab, as it is available on the "Situations" page. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

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

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-645: ---------------------------------- Could you add this information to the swyd forum thread, as they may have additional suggestions? > 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.1.0.Beta2 > > > 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)

9 years, 8 months

1
0
0 / 0

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

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.... ] Werner Müller commented on RTGOV-645: ------------------------------------- Ok, now I can confirm that a proper setting of Context Mapper parameters makes (3) work. The issue with this solution is that it requires us to change the setup of several Context Mappers. We currently have some Context Mappers with "Include Namespaces" set. '_rtogv_resubmittedSituationId' has no namespace. So I would have to add an empty namespace. How do you do that? My solution was to add the regex '^$', but this looks rather clumsy. In adiiton, it now maps all properties with an empty namespace. To solve this, you would need to add all required property names (from all namespaces) to the "Includes" parameter. (This is still gives you potentially more than expected.) OTOH, if you use the default setting of the context mapper parameters with no entry, SY adds '.*' to the Excludes parameter. This again filters out everything, including the '_rtogv_resubmittedSituationId'. IMO, the mapping of internal properties (like '_rtogv_resubmittedSituationId') should be transparent to application developers and not be controlled by the application's setting of context mappers or their parameters. > 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.1.0.Beta2 > > > 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-467) UI: relationship visualizations

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-467?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-467: ----------------------------------- Eric's prototype from Summit 2014: https://github.com/EricWittmann/summit-2014/tree/master/src/main/demo > UI: relationship visualizations > ------------------------------- > > Key: ARTIF-467 > URL: https://issues.jboss.org/browse/ARTIF-467 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-653) Persistent filter criteria on Situations page

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-653?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-653: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/285, https://github.com/Governance/rtgov/pull/286 (was: https://github.com/Governance/rtgov/pull/285) > Persistent filter criteria on Situations page > --------------------------------------------- > > Key: RTGOV-653 > URL: https://issues.jboss.org/browse/RTGOV-653 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > The filter criteria on the "Situations" page should be preserved during the session. > Currently they are cleared when you navigate away from that page. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-653) Persistent filter criteria on Situations page

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-653?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-653. ------------------------------ Resolution: Done > Persistent filter criteria on Situations page > --------------------------------------------- > > Key: RTGOV-653 > URL: https://issues.jboss.org/browse/RTGOV-653 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > The filter criteria on the "Situations" page should be preserved during the session. > Currently they are cleared when you navigate away from that page. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-653) Persistent filter criteria on Situations page

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-653?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-653: ----------------------------- Fix Version/s: 2.1.0.Beta2 > Persistent filter criteria on Situations page > --------------------------------------------- > > Key: RTGOV-653 > URL: https://issues.jboss.org/browse/RTGOV-653 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > The filter criteria on the "Situations" page should be preserved during the session. > Currently they are cleared when you navigate away from that page. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues April 2015