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

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

Commit 9df1b544b652ca619f5690e302e65963c93963a0 in airavata-django-portal's 
branch refs/heads/develop from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=9df1b54 ]

Merge pull request #53 from akbranam/develop

AIRAVATA-3366: Adding search options to the experiment list

> Improvement: Usr should be able to filter and search through experiments in 
> Experiment Browse
> ---------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-3366
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3366
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Django Portal
>    Affects Versions: 0.19
>         Environment: All gateways
>            Reporter: Eroma
>            Assignee: Anna Branam
>            Priority: Major
>             Fix For: 0.19
>
>
> # User A shared a 3-month-old experiment with all the gateway user group 
> users.
>  # User B is trying to view it, but its hard to get to it as there is no way 
> to search for it in the experiment browse.
>  # Users should be able to search for an experiment 
>  ## By created date range
>  ## By Application
>  ## By created user (When it comes to shared ones)
>  ## Submitted compute resource
>  ## Compute resource generated job ID (we can give a string field and filter 
> as the user search.)
>  # Any other that could make it easy for users.
>  # For gateway admins every experiment in the gateway is listed. For them to 
> find their own submissions, it would be better to have a checkbox to say 
> 'Show mine' and then further filter using the above filters. 
> h5. UI Mockup
> [https://ujt57q.axshare.com/#g=1&p=experiments-list]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to