April 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-311) Add support for comments associated with an Artifact

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-311?page=com.atlassian.jira.plugin.... ] Brett Meyer reassigned ARTIF-311: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Add support for comments associated with an Artifact > ---------------------------------------------------- > > Key: ARTIF-311 > URL: https://issues.jboss.org/browse/ARTIF-311 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > Add a UI around commenting on artifacts in the repository. Each comment should be its own artifact in the repository with a relationship to the artifact being discussed. The artifact type should be something like: > /ext/ArtifactComment -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-311) Add support for comments associated with an Artifact

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-311?page=com.atlassian.jira.plugin.... ] Work on ARTIF-311 started by Brett Meyer. ----------------------------------------- > Add support for comments associated with an Artifact > ---------------------------------------------------- > > Key: ARTIF-311 > URL: https://issues.jboss.org/browse/ARTIF-311 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > Add a UI around commenting on artifacts in the repository. Each comment should be its own artifact in the repository with a relationship to the artifact being discussed. The artifact type should be something like: > /ext/ArtifactComment -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-664: ------------------------------ Fix Version/s: (was: 1.1.0.Final) (was: 1.0.0.Beta1) > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 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 updated ARTIF-467: ------------------------------ Fix Version/s: 1.1.0.Final 1.0.0.Beta1 > 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, 2 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.... ] Work on ARTIF-467 started by Brett Meyer. ----------------------------------------- > 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 > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 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 updated ARTIF-467: ------------------------------ Git Pull Request: https://github.com/ArtificerRepo/artificer/pull/517 > 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 > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

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

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ] Werner Müller commented on RTGOV-649: ------------------------------------- At the moment we are working in synchronous mode only. But very likely we will need to move to async processing in the near future. So, it would be good to also have the re-open feature. > 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, 2 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 updated RTGOV-650: -------------------------------- Description: A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. Environment: (was: A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request.) > 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 > Reporter: Werner Müller > Assignee: Gary Brown > > 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, 2 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: ------------------------------------- Some additional Information: (1) => https://issues.jboss.org/browse/RTGOV-650 (2) The properties from RequestReceived were not set in the EPN. After setting those properties, it works fine. Thanks for the hint. (3) This is not a security issue. The "Required policies missing" exception is expected. The problem is that this exception is displayed as root situation. Here is some additional information: We are dealing here with two Services (let's call them [A] and [B]). A message is sent to [A] and then, via JMS, passed on to [B]. The schema is validated in [A]. The clientAuthentication is tested in [B]. When resubmitting after correcting the first error (Schema Validation), I can see in the message trace, that the resubmitted message's property '_rtgov_resubmittedSituationId' exists until the message leaves [A]. As soon as it enters [B], the property is gone Hope this helps. (4) Great. (5) At the moment, I'm not able to reproduce this. (6) => https://issues.jboss.org/browse/RTGOV-651 (7) Good. (8) Is the same as (6). Sorry about that. (9) => https://issues.jboss.org/browse/RTGOV-652 (10) => https://issues.jboss.org/browse/RTGOV-653 > 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, 2 months

1
0
0 / 0

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

by Werner Müller (JIRA)

Werner Müller created RTGOV-653: ----------------------------------- Summary: 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 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, 2 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