... | ... | @@ -25,7 +25,7 @@ Currently the interface implemented in the Operations Portal is split into 4 par |
|
|
* JIRA details page
|
|
|
* Service Order Management page
|
|
|
|
|
|
## Service order list
|
|
|
### Service order list
|
|
|
|
|
|
* Url : https://operations-portal.egi.eu/sombo/tickets
|
|
|
|
... | ... | @@ -50,3 +50,16 @@ In each section you can access the information related to a given order and depe |
|
|
![sombo3](uploads/8bb83dc81849a57cf4d9f780c2f24be5/sombo3.png)
|
|
|
|
|
|
This page allows the administrators of the tool to add/remove users to a group of services. The service order is associated with a service and only users authorized within this service will be able to treat the request . An additional role has been defined to browse all service orders .
|
|
|
|
|
|
# Jira Details Page
|
|
|
|
|
|
* Example of URL: https://operations-portal.egi.eu/sombo/tickets/edit/EOSCSOPR-326/EOSCSOPR-325
|
|
|
|
|
|
The JIRA details page summarises all information registered in JIRA and allows authorized users to modify it, they can also change the status of the request in agreement with the workflow. The authorization is based on the declarations done in the authorization page.
|
|
|
|
|
|
This page is showing details about the service order itself but also to the associated project (Epic Issue in Jira) and there is also the possibility to add comments :
|
|
|
* comments registered in Jira for the resource requestor (to ask for details, explanations …)
|
|
|
* internal comments for shifters (to exchange information about a request for example)
|
|
|
|
|
|
![sombo4](uploads/f62ec4a72bdd06ecb0d752f0ea9ef789/sombo4.png)
|
|
|
|