GitHub user doanduyhai opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/739

    [ZEPPELIN-687] Display paragraph id in config dropdown menu

    ### What is this PR for?
    Display paragraph id in the config drop down menu
    
    <em>This is a sub-task of epic **[ZEPPELIN-635]**</em>
    
    ### What type of PR is it?
    [Improvement]
    
    ### Todos
    * [ ] - Trivial code review & test
    
    ### Is there a relevant Jira issue?
    **[ZEPPELIN-687]**
    
    ### How should this be tested?
    1. Create any note
    2. Click on the config drop down menu of any paragraph to see the paragraph 
id
    
    ### Screenshots (if appropriate)
    
![image](https://cloud.githubusercontent.com/assets/1532977/13220573/3675ddf2-d977-11e5-98c5-a1c04df92c3c.png)
    
    ### Questions:
    * Does the licenses files need update? --> **No**
    * Is there breaking changes for older versions? --> **No**
    * Does this needs documentation? --> **No**
    
    [ZEPPELIN-687]: https://issues.apache.org/jira/browse/ZEPPELIN-687
    [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635

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

    $ git pull https://github.com/doanduyhai/incubator-zeppelin ZEPPELIN-687

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

    https://github.com/apache/incubator-zeppelin/pull/739.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 #739
    
----
commit 4aa4a7979fc287ef86b19ed4a710c88cdcbd6a69
Author: DuyHai DOAN <doanduy...@gmail.com>
Date:   2016-02-22T14:15:54Z

    [ZEPPELIN-687] Display paragraph id in config dropdown menu

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to