JIRA Confluence Portlet

Added by Jonathan Nolen, last edited by David Chui on Apr 17, 2008  (view change) show comment
Name JIRA Confluence Portlet
Vendor Tommi Laukkanen (Website)
Authors Atlassian
Homepage http://confluence.atlassian.com/display/JIRAEXT/JIRA+Confluence+Portlet
Issue Management http://developer.atlassian.com/jira/browse/JCP
Categories Remote Access
Version 1.0.2
Availability JIRA v3.8.1 to v3.13
State Stable
Support Unsupported Plugins
License Freeware / Open Source (BSD)
Price Free
Release Docs http://developer.atlassian.com/jira/browse/JCP
Java API Docs n/a
Download Source http://svn.atlassian.com/svn/public/contrib/jira/jira-confluence-portlet/tags/confluence-page-portlet-1.0.2/
Download JAR confluence-page-portlet-1.0.2.jar

Description/Features

A JIRA Portlet that can display a single Confluence page (just the content, not the app chrome) and an edit link. User can configure Confluence instance, space and page which is displayed in the JIRA's dashboard portlet.
Portlet is great for showing company news from Confluence or showing selected RSS feed nicely formatted by the Confluence.

Usage

  1. Install the plugin by downloading the plugin JAR
  2. Place the downloaded JAR file to <JIRA>/atlassian-jira/WEB-INF/lib folder
  3. restart JIRA
  4. On the dashboard view click Configure ON
  5. Click "Add a new portlet"
  6. Select "Confluence Page" portlet and click "Add"
  7. Enter the configuration data
    1. Confluence instance URL should point to Confluence server e.g. http://myconfluence:8080
    2. Confluence username is the username that you use for Confluence
    3. Password for Confluence should match your password for Confluence
    4. Confluence space key is a key for the Confluence Space where selected page is located in. e.g. Demonstration Space has a key "ds". This can be seen from URL address or from space administration view.
    5. Confluence page title is a page title that should be shown. Page should locate in the space that was defined with the space key.
    6. Click "Save" to save your configuration
  8. Now you should be viewing a portlet that contains Confluence page content.

Examples

Here is an example where user will create a "Hello World" Confluence page and display it on the JIRA dashboard portlet:

1. First new page is added to Confluence
2. New portlet instance is added ...
3. ... and configured to JIRA
4. New portlet displays "Hello World" page

Version History

Version Date Description
1.0 May 11th 2007 Initial version
1.0.1 May 12th 2007 Fixed the image and href links
1.0.2 Apr 18th 2008 Migrated to Maven 2

Screenshots

Screenshots
Portlet in action
Portlet configuration
Configure portlet
Add new portlet to dashboard
Add new page to Confluence
Confluence News and RSS example

Labels

codegeist_2007_jira codegeist_2007_jira Delete
jira jira Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (14)

 

  1. May 16, 2007

    Bob Swift says:

    Nice idea! However, there is a restriction in that normal linking on the Conflue...

    Nice idea! However, there is a restriction in that normal linking on the Confluence page does not work. For instance, a page reference link fails since the page uses links like href="/display/spacekey/page+name" which are not found on the jira server. Unless you know of away around this, it limits the type of page that could be shown this way.

    1. May 16, 2007

      Tommi Laukkanen says:

      Thanks! Normal page linking works with this plugin. I noticed this problem while...

      Thanks! Normal page linking works with this plugin. I noticed this problem while developing the plugin and I solved it by simply replacing all href="/ with href="<confluenceurl>/. Same problem occurs also with the icons but I solved it the same way.

      1. May 16, 2007

        Bob Swift says:

        Well, its not working in our installation.

        Well, its not working in our installation.

        1. May 17, 2007

          Tommi Laukkanen says:

          Did you download the JAR from my homepage? My homepage had the old version. This...

          Did you download the JAR from my homepage? My homepage had the old version. This page contains the latest version 1.0.1 that should include the fix. Can you check what the version is in your JAR filename? It should be confluence-page-portlet-1.0.1.jar

          I removed the downloads from my homepage and pointed the link to this page as it is easier to update the version only to one place.

          1. May 17, 2007

            Bob Swift says:

            1.0.1 works. Thanks.

            1.0.1 works. Thanks.

            1. May 17, 2007

              Tommi Laukkanen says:

              Great! I hope you find the plugin useful.

              Great! I hope you find the plugin useful.

  2. Mar 20

    Doods Perea says:

    I just tested this on JIRA 3.12.2 and it worked. (y)\\

    I just tested this on JIRA 3.12.2 and it worked.

  3. May 08

    Jamie says:

    Would be great if this could work using the new trusted protocol... so you didn'...

    Would be great if this could work using the new trusted protocol... so you didn't put a password in, and it used the credentials of the user currently logged in to jira.

  4. May 18

    ben jones says:

    Hi Guys, I was testing out this portlet on a JIRA 3.12 instance today and came a...

    Hi Guys,

    I was testing out this portlet on a JIRA 3.12 instance today and came across a major problem. If confluence is down, the portlet causes the JIRA dashboard containing the portlet to not display itself thus rendering JIRA basically unusable. Shouldn't it have some sort of error message that is displayed telling you that the link to confluence is down or not accessible?

    Ben 

  5. May 30

    Doods Perea says:

    I got the following in JIRA when I tried it in our Production environment where ...

    I got the following in JIRA when I tried it in our Production environment where JIRA and Confluence are on different servers:

    "Error while loading Confluence page. Check configuration and/or log files."

    When I checked the "stdout_20070527.log" file I found this portion of the entry:

    "http-8080-Processor29 WARN [atlassian.seraph.auth.DefaultAuthenticator] User: tried to login but they do not have USE permission or weren't found. Deleting cookie.
    Avoiding obscuring previous error by supressing error encountered while ending request: org.apache.xmlrpc.XmlRpcClientException: Exception closing URLConnection
    java.net.ConnectException: Connection timed out: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
    ...." 

    I am quite sure I used the correct username and password, and the required Confluence url, spacekey, and page title.

    Can anyone please help me resolve this?

    Thanks very much.

    Doods

    1. Jun 29

      Doods Perea says:

      I still could not fix the issue above and wonder if anyone can help me, please. ...

      I still could not fix the issue above and wonder if anyone can help me, please.

      Our production JIRA and Confluence installations are on different servers.

      Thanks,

  6. Jun 02

    Igor V Demin says:

    &nbsp;&nbsp; I think your problem is in "https" so you need certificate&nbsp;on ...

       I think your problem is in "https" so you need certificate on each of both sides.

    1. Jun 02

      Doods Perea says:

      Thanks Igor but we don't use https in both JIRA and Confluence. Also, in our Pre...

      Thanks Igor - but we don't use https in both JIRA and Confluence.

      Also, in our Pre-Production server (where both JIRA and Confluence are installed), I did not have to configure https for them and it worked.

      Regards, 

  7. Aug 14

    Liz leach says:

    Plugin working great in JIRA v3.12.3 with Confluence 2.9. Couple of questions 1)...

    Plugin working great in JIRA v3.12.3 with Confluence 2.9. Couple of questions

    1) Is the issue identified above by Ben where the JIRA dashboard doesn't render at all if confluence is unavailable now fixed? I noticed that you get a properly rendered error if the wrong user credentials are supplied in the configuration of the portlet.

    2) Is there any way to remove the [Edit] option either conditionally based on user security access or as an option on the configuration of the portlet.

    Finally, I'd second Jamie's comment above regarding trusted application support although I'm not sure if this is supported when pulling information from Confluence into JIRA rather than the other way around.