[ 
https://issues.apache.org/jira/browse/AIRAVATA-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551051#comment-17551051
 ] 

ASF subversion and git services commented on AIRAVATA-3574:
-----------------------------------------------------------

Commit fe5b308210ec3f42a48c6003d3512b37471bc797 in airavata-django-portal's 
branch refs/heads/delta-topology-workshop from Dinuka De Silva
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=fe5b3082 ]

AIRAVATA-3574: Fix application description in experiment edit


> Ability to add a central description to the Django Portal workspace.
> --------------------------------------------------------------------
>
>                 Key: AIRAVATA-3574
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3574
>             Project: Airavata
>          Issue Type: New Feature
>          Components: Django Portal
>            Reporter: Eroma
>            Assignee: Dinuka Subashana De Silva
>            Priority: Major
>
> In the Django Portal at application level and individual application input 
> level we can add a description. The description would have information and 
> even URLs to get more information.
> The new feature is to have the same at gateway level. This would be for 
> gateway admins to add and users to consume.
> This to appear in workspace, above the listened applications. 
> A gateway admin can choose to have or not have this in their gateway. The 
> description will simply appear if exists and if not, the section won't even 
> appear.
>  
> Gateway admins should be able to add this description, edit it and delete if 
> not needed. This could also be used for temporarily description as well, may 
> be when the gateway is launched, but after it may be not needed.
> When this section is available, and the user will always be able to see this. 
> A future development would be to have the option of saying 'Don't show 
> anymore' for individual users.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to