April 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-649) Status handling for Situations

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-649: ---------------------------------- Hi Werner, The changes have been merged into the 2.0.x branch. As there are a number of different aspects to this feature, would it be possible for you to build the branch from source and make sure it achieves what you require? NOTE: to set the resolution state change to auto only (no buttons on UI), you will need to add the property "UI.manualResolution" with value 'false' (default is true) into the standalone-full.xml under the "overlord-rtgov" property section. To build, use "mvn -Pdocs clean install" from the root folder. If any problems let me know and I can upload a build somewhere. > Status handling for Situations > ------------------------------ > > Key: RTGOV-649 > URL: https://issues.jboss.org/browse/RTGOV-649 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Werner Müller > Assignee: Gary Brown > > This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed: > - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED: > Either remove other values, or provide means to configure the values. > - The default entry for the Status filter on the Situations page shall be (the new value) OPEN: > This includes all Status values other than RESOLVED. > > - A Situation's Status should be changed only programmatically (see below): > Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration. > > - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'. > (This is to be consistent with the resubmit behaviour as defined below.) > - The initial state of a (root) Situation is UNRESOLVED. > When a Situation is resubmitted: > (1) 'assignedTo' is set to the current user (overriding the current value) > (2a) If no failure is encountered (no child situation is created), > the Status is changed to RESOLVED. > (2b) If a failure is encountered (and a child situation is created), > the Status is changed to IN_PROGRESS. > - A Situation in Status RESOLVED must not be resubmitted anymore: > (1) The Resubmit button on the "Message" tab is disabled. > (2) The Situation is excluded from a bulk resubmit. > > As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-649) Status handling for Situations

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-649: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/291 > Status handling for Situations > ------------------------------ > > Key: RTGOV-649 > URL: https://issues.jboss.org/browse/RTGOV-649 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Werner Müller > Assignee: Gary Brown > > This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed: > - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED: > Either remove other values, or provide means to configure the values. > - The default entry for the Status filter on the Situations page shall be (the new value) OPEN: > This includes all Status values other than RESOLVED. > > - A Situation's Status should be changed only programmatically (see below): > Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration. > > - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'. > (This is to be consistent with the resubmit behaviour as defined below.) > - The initial state of a (root) Situation is UNRESOLVED. > When a Situation is resubmitted: > (1) 'assignedTo' is set to the current user (overriding the current value) > (2a) If no failure is encountered (no child situation is created), > the Status is changed to RESOLVED. > (2b) If a failure is encountered (and a child situation is created), > the Status is changed to IN_PROGRESS. > - A Situation in Status RESOLVED must not be resubmitted anymore: > (1) The Resubmit button on the "Message" tab is disabled. > (2) The Situation is excluded from a bulk resubmit. > > As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-650. ------------------------------ Resolution: Done > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Werner Müller commented on RTGOV-650: ------------------------------------- Yes, that's fine with me. > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-650: ---------------------------------- Will fix this as part of the work on RTGOV-649 (as already under way) - so unless there is anything else, can this issue be marked as resolved? > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Werner Müller reopened RTGOV-650: --------------------------------- > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-650: ---------------------------------- Woops :( - thanks for spotting that, will get that fixed. > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Werner Müller commented on RTGOV-650: ------------------------------------- Although it is not the ultimate solution (it causes additional setup steps) we can live with this property - with one exception: In SwitchYardResubmitActionProvider#resubmit(...) there is the loop over the urls. This loop ends in the try block with a 'continue'. Presumably, this should be a 'break'. Otherwise you run into different issues. > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-650: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/289, https://github.com/Governance/rtgov/pull/290 (was: https://github.com/Governance/rtgov/pull/289) > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-650. ------------------------------ Resolution: Done > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues April 2015