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

ASF GitHub Bot commented on AIRAVATA-2032:
------------------------------------------

GitHub user machristie opened a pull request:

    https://github.com/apache/airavata-php-gateway/pull/50

    AIRAVATA-2032 Fix closing exp summary tabs

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/machristie/airavata-php-gateway 
AIRAVATA-2032-experiment-statistics-page-cannot-close-the-tabs

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/airavata-php-gateway/pull/50.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #50
    
----
commit a0391c9a4f71dd45646161d528f1914029dcad5c
Author: Marcus Christie <machr...@iu.edu>
Date:   2016-12-02T01:06:47Z

    AIRAVATA-2032 Fix closing exp summary tabs

----


> In PGA --> Admin Dashboard --> Experiment Statistics page cannot close the 
> tabs opened due to searching experiments
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2032
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2032
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>            Reporter: Eroma
>            Assignee: Marcus Christie
>             Fix For: 0.17-SNAPSHOT
>
>         Attachments: Screen Shot 2016-09-29 at 3.11.16 PM.png
>
>
> Gateway admin can search for specific experiment by giving the experiment ID 
> in above path.
> When searched for an experiment, details open in a new tab.
> for each experiment ID searched a new tab will open (which is OK)
> But we need to give close button for each of these tabs. No way of closing 
> them currently



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to