You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2018/12/24 19:28:00 UTC

[jira] [Updated] (AIRAVATA-2964) SciGaP admins, Gateway admins/PIs communicating with gateway users

     [ https://issues.apache.org/jira/browse/AIRAVATA-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eroma updated AIRAVATA-2964:
----------------------------
    Description: 
This task is to handle and implement communication between SciGaP team (Gateway providers) and gateway users.
 # Multiple groups of gatew users are available.
 # Gateway user groups are admin, gateway user, groups created by gateway users, admins, etc
 # SciGaP admins/team need a way to communicate with either all the user groups or selected user groups for a specific gateway or for all gateway.
 # The communication could be through email, or if the users have provided phone number and want to receive text messages. Sending text messages could be the second phase of this implementation. Emails of users are already there in the system and we could start with email.
 # The communication could be to inform unavailability of system, specific compute resources maintenance, nw application release, etc...
 # Currently the notices are only for users when they login to the gateway portal.
 # Similar to SciGaP team reaching out to users gateway PIs should be able to email selected users, user groups through the same method.

  was:
This task is to handle and implement communication between SciGaP team (Gateway providers) and gateway users.
 # Multiple groups of gatew users are available.
 # Gateway user groups are admin, gateway user, groups created by gateway users, admins, etc
 # SciGaP admins/team need a way to communicate with either all the user groups or selected user groups for a specific gateway or for all gateway.
 # The communication could be through email, or if the users have provided phone number and want to receive text messages. Sending text messages could be the second phase of this implementation. Emails of users are already there in the system and we could start with email.
 # The communication could be to inform unavailability of system, specific compute resources maintenance, nw application release, etc...
 # Currently the notices are only for users when they login to the gateway portal.

        Summary: SciGaP admins, Gateway admins/PIs communicating with gateway users  (was: Communicating with Gateway Users)

> SciGaP admins, Gateway admins/PIs communicating with gateway users
> ------------------------------------------------------------------
>
>                 Key: AIRAVATA-2964
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2964
>             Project: Airavata
>          Issue Type: Task
>          Components: Airavata System, Django Portal, PGA PHP Web Gateway
>    Affects Versions: 0.18
>            Reporter: Eroma
>            Priority: Major
>             Fix For: 0.18
>
>
> This task is to handle and implement communication between SciGaP team (Gateway providers) and gateway users.
>  # Multiple groups of gatew users are available.
>  # Gateway user groups are admin, gateway user, groups created by gateway users, admins, etc
>  # SciGaP admins/team need a way to communicate with either all the user groups or selected user groups for a specific gateway or for all gateway.
>  # The communication could be through email, or if the users have provided phone number and want to receive text messages. Sending text messages could be the second phase of this implementation. Emails of users are already there in the system and we could start with email.
>  # The communication could be to inform unavailability of system, specific compute resources maintenance, nw application release, etc...
>  # Currently the notices are only for users when they login to the gateway portal.
>  # Similar to SciGaP team reaching out to users gateway PIs should be able to email selected users, user groups through the same method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)