=== Background ===

{{excerpt}}
The Confluence page gadget allows you to show content from a page on your Confluence site in a gadget, allowing users to subscribe to and share individual gadgets between Confluence and JIRA.
{{/excerpt}}

=== High-level Use Cases ===

Below is a brainstorm of some possible use cases that could be achieved with the Confluence Page Gadget inside a JIRA dashboard:

1. Link to all your important project documentation directly in the JIRA dashboard:
11. Create a shared JIRA dashboard for the Confluence 3.3 release
11. Embed a Confluence activity stream gadget showing updates to the CONFDEV space
11. Embed a page with the //content-by-label// macro that just shows pages with the "3//3//meetings" label
11. Embed a page that has the //blog// macro showing each milestone blog post
11. Add a page gadget that has links to high level goals and features for the release
1. A basic text editor inside a JIRA dashboard
11. A project status page showing project status color and some text commentary explaining the status. You'll need to be able to edit it from JIRA
1. Other benefits of embedding a Confluence page inside a JIRA dashboard:
11. Embed slideshows and excel spreadsheets using the Office Connector
11. Embed SQL charts and queries
11. Embed images and widgets
11. Embed a list of attachments

=== Assumptions ===

* [[OAuth Trusted relationship is already setup>>http://confluence.atlassian.com/display/DOC/Adding+a+Confluence+Gadget+to+a+JIRA+Dashboard#AddingaConfluenceGadgettoaJIRADashboard-EstablishanOAuthorTrustedApplicationRelationshipBetweenConfluenceandJIRA]] in the destination application.
* There already exists a Confluence page in a wiki which the user wishes to 'gadgetise'.
* We will **not** allow users to create new pages from the page gadget.
* We will **not** display comments on a page within the Confluence page gadget

===  ===

=== Requirements ===

|= User Story Title |= User Story Description |= Priority Order |= Notes 
 
| Adding the Gadget | Andy the Administrator wants to allow his JIRA users to display a Confluence page on their dashboard. He wants to do this so that Karen the creator can easily share her requirements from Confluence with her engineering team who spend most of their time in JIRA. \\

* The Confluence page gadget is available for any JIRA user to use.
* The page gadget does not require additional authentication details to setup. | 1 
 | Andy should be able to add the page gadget from another Confluence instance his Confluence instance (not just form Confluence->JIRA and visa-versa) 
\\\\ 
| Selecting a Confluence Page to display | Dave the Developer wants to display a listing of all the requirements Karen created in his JIRA dashboard, so that he can easily reference them as he works in JIRA. Karen has already created the requirements and linked them all on a Confluence page using a //conent-by-label// macro. \\

* He adds the Gadget via the JIRA gadget browser
* He //searches// for the Confluence page his is after from the JIRA gadget and selects it. 
\\OR 
\\He could paste the URL / configure the base URL, space key & page title.
* He should also be able to display pages with:
** images
** embedded content (pdf / ppt) as they appear in Confluence (flash)
** macros | 2 
 | Dave should be able to display multiple page gadgets on the same JIRA/Confluence page. 
\\\\\\If a Confluence page gadget is displayed in Confluence, you can choose the width of it. If it's in JIRA, it will resize to the appropriate fluid layout 
 
| Changing the Page Gadget settings | Dave the Developer notices that Karen is frequently changing the requirements (classic Karen{{{!}}}). He wants to configure the gadget to refresh frequently and change the specification page he is referencing so that he can make sure he has the latest page. He can edit the gadget settings and change: \\

* the refresh internal
* the page title / location
* the title of the gadget
* other items (see "Gadget Config Parameters" below) | 3 
 | 
| Browsing from within the Confluence Page Gadget | Dave can now see Karen's list of requirements from his JIRA dashboard. 
\\He would like further detail on one of the specifications, so he clicks on a link to one of the specs from within the page gadget. This opens up a Confluence page in a new window, taking Dave is now away from the JIRA environment where he can now read, edit and comment on the spec. 
\\\\ | 4 
 | 
 
| Editing the Confluence page 
 | Dave the developer has completed some of the requirements Karen had for him. He wants to edit the Confluence page within the gadget so that he can collaborate with Karen and let her know the item is complete. \\

* He presses the "edit page" link from the JIRA gadget. Given he has the appropriate permissions, the Confluence edit page opens in a new window.
* He then makes the changes and presses save.
* The user then closes the new window, so they are back to the JIRA dashboard.
* The Confluence page gadget has **{//}picked up{//}** the page state has changed, and 'fades' in gray with a message "Confluence page has changed, please refresh the gadget". (Not sure how possible this is) | 5 
 | Could have a "view" and "edit" link which just take you back to Confluence. 
\\\\\\Ideal: 
\\The below could be technically very time consuming. Up for discussion. \\

* User clicks edit
* The gadget 'maximises' into a full-screen gadget, where the user has the normal editing Experience in Confluence but in JIRA.
* User makes the changes he wants and updates the status of the requirements
* User hits "save" and saves the page
* The gadget is 'shrunk' back down to it's original layout position and refreshed with the latest changes. 
\\Ideally: We don't want the user to leave the JIRA dashboard when they want to make a quick edit 
 