[JBoss JIRA] (RTGOV-330) Allow situations to be allocated/assigned to individual
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-330?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-330.
------------------------------
Resolution: Done
> Allow situations to be allocated/assigned to individual
> -------------------------------------------------------
>
> Key: RTGOV-330
> URL: https://issues.jboss.org/browse/RTGOV-330
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Components: User Interface
> Reporter: Gary Brown
> Assignee: Michael Clay
>
> Allow a situation to be assigned to a user. To avoid maintaining list of users (for now), we will use a ‘take’ approach, so the currently logged in user can ‘take’ responsibility for a situation (if not already associated with another user). This will result in their username being associated with a property on the situation, and the situation being recorded back to the db.
> Once the user is responsible for the situation, they should have the ability to set its status. Current status values will be Unresolved (default value upon a situation being assigned) and Resolved.
> To avoid the scenario where a situation remains associated with a user while no action is being taken, it should be possible for a more privileged user to be able to 'take' it from another assigned user. This may only happen if this user has a 'management' role - to be discussed further.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RTGOV-354) Situation Assignment not working in EAP environment
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-354?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-354.
------------------------------
Resolution: Done
> Situation Assignment not working in EAP environment
> ---------------------------------------------------
>
> Key: RTGOV-354
> URL: https://issues.jboss.org/browse/RTGOV-354
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Eric Wittmann
> Assignee: Michael Clay
>
> The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it.
> As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered.
> Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService):
> {code}
> @Inject javax.enterprise.inject.Instance<VoidHandler> voidHandlerFactory;
> VoidHandler vh = voidHandlerFactory.get();
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RTGOV-354) Situation Assignment not working in EAP environment
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/RTGOV-354?page=com.atlassian.jira.plugin.... ]
Eric Wittmann reassigned RTGOV-354:
-----------------------------------
Assignee: Michael Clay
> Situation Assignment not working in EAP environment
> ---------------------------------------------------
>
> Key: RTGOV-354
> URL: https://issues.jboss.org/browse/RTGOV-354
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Eric Wittmann
> Assignee: Michael Clay
>
> The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it.
> As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered.
> Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService):
> {code}
> @Inject javax.enterprise.inject.Instance<VoidHandler> voidHandlerFactory;
> VoidHandler vh = voidHandlerFactory.get();
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RTGOV-354) Situation Assignment not working in EAP environment
by Eric Wittmann (JIRA)
Eric Wittmann created RTGOV-354:
-----------------------------------
Summary: Situation Assignment not working in EAP environment
Key: RTGOV-354
URL: https://issues.jboss.org/browse/RTGOV-354
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Eric Wittmann
The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it.
As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered.
Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService):
@Inject javax.enterprise.inject.Instance<VoidHandler> voidHandlerFactory;
VoidHandler vh = voidHandlerFactory.get();
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RTGOV-354) Situation Assignment not working in EAP environment
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/RTGOV-354?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated RTGOV-354:
--------------------------------
Description:
The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it.
As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered.
Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService):
{code}
@Inject javax.enterprise.inject.Instance<VoidHandler> voidHandlerFactory;
VoidHandler vh = voidHandlerFactory.get();
{code}
was:
The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it.
As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered.
Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService):
@Inject javax.enterprise.inject.Instance<VoidHandler> voidHandlerFactory;
VoidHandler vh = voidHandlerFactory.get();
> Situation Assignment not working in EAP environment
> ---------------------------------------------------
>
> Key: RTGOV-354
> URL: https://issues.jboss.org/browse/RTGOV-354
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Eric Wittmann
>
> The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it.
> As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered.
> Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService):
> {code}
> @Inject javax.enterprise.inject.Instance<VoidHandler> voidHandlerFactory;
> VoidHandler vh = voidHandlerFactory.get();
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RTGOV-330) Allow situations to be allocated/assigned to individual
by Michael Clay (JIRA)
[ https://issues.jboss.org/browse/RTGOV-330?page=com.atlassian.jira.plugin.... ]
Work on RTGOV-330 started by Michael Clay.
> Allow situations to be allocated/assigned to individual
> -------------------------------------------------------
>
> Key: RTGOV-330
> URL: https://issues.jboss.org/browse/RTGOV-330
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Components: User Interface
> Reporter: Gary Brown
> Assignee: Michael Clay
>
> Allow a situation to be assigned to a user. To avoid maintaining list of users (for now), we will use a ‘take’ approach, so the currently logged in user can ‘take’ responsibility for a situation (if not already associated with another user). This will result in their username being associated with a property on the situation, and the situation being recorded back to the db.
> Once the user is responsible for the situation, they should have the ability to set its status. Current status values will be Unresolved (default value upon a situation being assigned) and Resolved.
> To avoid the scenario where a situation remains associated with a user while no action is being taken, it should be possible for a more privileged user to be able to 'take' it from another assigned user. This may only happen if this user has a 'management' role - to be discussed further.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months