Release Status Plugin

Name Release Status
Version 2.4.3
Product Versions 3.13
Author(s) Henri Yandell/SourceLabs, Inc.
License Apache License, 2.0
Download/Bugs etc JIRA Outlet

This project uses the excellent famfamfam.com Silk icons.

Description/Features

A plugin providing three portlets - a release status portlet, a latest releases portlet and a releases project panel.
1. The first is a portlet for the JIRA dashboard that provides a status for a particular version. Its expected use case is for highlighting the next release of the major product(s) via a feature-list of:

  • Handy stats on the activity in the last week
  • Useful stats for due-date management
  • Information on how close the project is to release
  • Release health - will your last week's velocity see you hitting your release date
  • Useful links to the release notes and the version workload
  • Current user, all users or adaptive toggle - adaptive means that between 50% and 95% it's current user, otherwise it's all users

2. The second portlet lets you show the last N releases. Its expected to be of use to large JIRAs with many releases.

3. The third is a project panel that makes it easy to see the release history of a project. Its expected to be of use to projects that have had with many releases.

Release History

Version 2.4.3 was released on 4th of November 2008. There was one bugfix:

  • JOUT-3 - Velocity Error with isVersionOverDue in Releases project tab

Version 2.4.2 was released on 30th of January 2008. There was one bugfix:

  • RSP-71 - Nothing shows when a project has only 1 version

Version 2.4.1 was released on 28th of September 2007. There were two bugfixes, the second of which was an improvement over its fix in 2.4:

  • RSP-68 - Fails to run under 3.11
  • RSP-63 - No Version Descritpion Text Causes $version.description is not a valid reference Exception

Version 2.4 was released on 4th of August 2007. There were four improvements and three bugfixes:

  • RSP-56 - Show a tick or a cross if at 100% or if the release date has been missed
  • RSP-57 - Need way to click on progress bar when it's small
  • RSP-58 - 'smart' default for currentuser/all
  • RSP-60 - Random project Release Status
  • RSP-61 - Right arrow is not vertically aligned to top when there's no emoticon
  • RSP-62 - Velocity Error with isVersionOverDue in Jira 3.10
  • RSP-63 - No Version Description Text Causes $version.description is not a valid reference Exception

Version 2.3.1 was released on 28th of July 2007. There were two bugfixes:

  • RSP-55 - Release Status Portlet generates exceptions under Jira 3.10
  • RSP-7 - Releases project tab links to unresolved issues, not all issues

Version 2.3 was released on 19th of April 2007. There were four bugfixes:

  • Latest Releases portlet was not showing more than one release for the same day
  • Release Status portlet links were not changing under current user mode
  • The Release Status portlet now ignores archived versions that are not released when deciding on a default version for a project
  • The direct link for the Release Status portlet was failing with an NPE when the portlet was showing just the one version

Version 2.2 was released on 13th of April 2007. It provided various bugfixes and small feature enhancements, including:

  • The Release Status portlet allows a project to be specified to show the status of all releases in that JIRA project
  • Tooltips are now escaped in case descriptions contain HTML
  • The Latest Releases portlet allows Future Releases and/or Overdue Releases to be shown
  • User's permissions to see projects is better heeded by both the Release Status portlet and the Latest Releases portlet
  • The Release Status portlet shows the total number of issues in a project
  • The number of issues In Progress is shown
  • Anonymous viewing is better

Version 2.1 was released on 27th of March 2007. Its main focus was a beefed up release status portlet with:

  • Now supports more than one version, allowing you to create version chains
  • The new top bar containing:
    o project name
    o current-user/all-users toggle
    o links to the release notes and the version workload report

Version 2.0 was released on 17th of March 2007. It added the latest releases portlet and the releases project panel.

Version 1.0 was released on 16th of March 2007. It just contained the release status portlet.

Installing & Using

Install the plugin by downloading the plugin jar, place it in your $JIRA/WEB-INF/lib/ and giving your JIRA a restart.

Once it's installed you can add the to your dashboard by selecting the Release Status portlet and the Latest Releases portlet. The Releases project tab is automatically added to your browse project pages. Please follow the instructions from Atlassian for configuring your personal dashboard or the default dashboard.

Previously Asked Questions

  • What's happiness? (or... The secret to happiness)
    • Obviously you're all wondering what makes happiness. How does one tell the health of a project. What secret bit of wizardry and hours of cpu-intensive magic is this portlet doing???
    • Fortunately, here at CBA Industries we decided to take the simple approach to happiness. It's simply: "If the project continues to maintain the velocity of the last 7 days, will it hit its release date?". Nothing fancy, nothing special and something to be taken with a LOT of salt. Amongst its limitations it includes non-work days as if they were normal days and it treats all issues the same regardless of estimate.
  • How do I see the open issues?
    • Most of the items in the release portlet are clickable. To see the current open issues, click on the green part of the progress bar. To see the closed issues, click on the red part. To see all the issues in a version, click on the version name.
  • How do I configure a list of versions?
    • Versions are added via a comma-separated list of ids on the portlet configuration page. Version ids can be found by mousing over a version link pretty much anywhere in JIRA (it will be called fixFor or version in the URL). You will see the link in the status bar at the bottom of your browser (you may need to turn on the Status bar).

Labels

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

Comments (62)

 

  1. Mar 27, 2007

    Bob Swift says:

    Release status portlet is very nice! Thank-you. Updated to 2.1 to get the chai...

    Release status portlet is very nice! Thank-you. Updated to 2.1 to get the chain of releases. I added a few versions ids (blank/line separated) to the configuration, but, still only get the default with no arrows.

    1. Apr 05, 2007

      Henri Yandell says:

      It's a comma separated list rather than one per line; with hindsight that seems ...

      It's a comma separated list rather than one per line; with hindsight that seems a daft decision

      For the moment I've updated the description to specify:

      "Comma separated list of versions to provide statuses for. If a version is specified above, it will be the default version. "

      I'll also add it to the "Previously Asked Questions" section on the webpage when I make a new release (soon, though nothing major in it).

      Thanks for highlighting that I wasn't explaining that at all Bob!

      1. Apr 05, 2007

        Bob Swift says:

        Thanks - that is easy enough! Should have tried that since I use that technique...

        Thanks - that is easy enough! Should have tried that since I use that technique all the time too! Can't verify now since I am back on 2.0 level.

  2. Mar 27, 2007

    Bob Swift says:

    Getting a NPE when I try to use 2.1 with Confluence jiraportlet macro. Works ok...

    Getting a NPE when I try to use 2.1 with Confluence jiraportlet macro. Works ok with 2.0 . This is what is in the jira log:

    java.lang.NullPointerException
	at com.sourcelabs.jira.plugin.portlet.releases.ReleaseStatusPortlet.getVelocityParams(ReleaseStatusPortlet.java:112)
	at com.atlassian.jira.portal.PortletImpl.getViewHtml(PortletImpl.java:68)
	at com.atlassian.jira.web.portlet.bean.PortletRenderer.getNormalHtml(PortletRenderer.java:83)

    1. Apr 05, 2007

      Henri Yandell says:

      I'll put this on the to-investigate list. I had a play with the jiraportlet macr...

      I'll put this on the to-investigate list. I had a play with the jiraportlet macro and the various portlets, but it's not a part of my usual testing process (which is to hit things with Firefox and IE7 and be happy its 2007 ).

      1. May 08, 2007

        Bob Swift says:

        Any update on this issue? Still a problem.

        Any update on this issue? Still a problem.

        1. Jul 04, 2007

          Henri Yandell says:

          Recorded as: https://jira.sourcelabs.org/jira/browse/RSP-50

          Recorded as: https://jira.sourcelabs.org/jira/browse/RSP-50

          1. Jul 31, 2007

            Henri Yandell says:

            Looking at this Bob, I can't reproduce it. I'm in quite a dated version of Confl...

            Looking at this Bob, I can't reproduce it. I'm in quite a dated version of Confluence - 2.1.1. Which version of Confluence are you on where you get the NPE? What's your input?

            Are you including the os_username, os_password parameters?

             I do notice that it stretches off to fill the page, and that the javascript stuff is completely broken as per other comments.

  3. Mar 27, 2007

    Bob Swift says:

    For use in Confluence, it would be nice to have the portlet be compact. Now it ...

    For use in Confluence, it would be nice to have the portlet be compact. Now it spreads itself over the entire page width and does not look very good. A good example is the single project portlet.

  4. Apr 03, 2007

    Vincent Eggen says:

    Very cool plugin. It's very promising. Having tried them a little bit, here is ...

    Very cool plugin. It's very promising.

    Having tried them a little bit, here is my first feedback:

    • New feature: add a "Future Releases" portlet. A lot of people (did I say "sales" ?) like having an quick idea of the release plan.
    • Improvement: don't add the Project Description to the header of the release status portlet (or at least make it configurable). Most of our PM have customized their project description with additional links to wiki pages, external URL references, mail adresses,...This is very useful for people browsing the project. And it's useless/confusing into the release status portlet.
    • Improvement: remove sub-tasks from these portlets filters scope (or at least, make it configurable). Most people interested by a release content are not interested by the related sub-tasks.

    1. Apr 05, 2007

      Henri Yandell says:

      Thanks for the list Vincent. What kind of things would you want in a Future R...

      Thanks for the list Vincent.

      • What kind of things would you want in a Future Releases portlet?

      The way I use the release-status portlet at work is to chain together both past and future releases, with the current release being the central one. I'm planning to make that easier to configure for projects who want all versions within that project to be in the chain, with the next planned release-date being the one to focus on.

      • Currently the project description is a mouseover, did the various HTML bits cause problems in the rendering? Maybe I just need to make sure I escape the HTML there. Making it configurable definitely seems good though - I want lots of configuration
      • Definitely a configurable option. Might slow things down a bit, JIRA tends not to have an easy way to say "NOT x", ie) "NOT type=subtask". I actually find that the ones I want to ignore are tasks with subtasks (as I never put work into a parent task, or an estimate), so I imagine it'll come down to people's usage patterns a lot.

      1. Apr 05, 2007

        Vincent Eggen says:

        Thanks for your answer. Regarding the Future Releases portlet, it can be as sim...

        Thanks for your answer.

        Regarding the Future Releases portlet, it can be as simple as the Latest Release one, but simply reporting the list of next releases from the current date. If we can also select a list of projects in the scope of the portlet, it's even better.

        I think your guess is rigth for the project description issue: the "embedded" html created by our PM is breaking the mouseover. A simple

        <P>
<FONT face=Arial size=2>
<A title="Iteration Backlog" href="http://xxx" >
Iteration Backlog
</A>
</FONT>
</P>

        breaks the view.

        For the sub-task issue, it's definitelly related to a usage pattern: we do feature driven development using Jira. And we do our estimates right at the parent issue level. Sub-tasks are only used for intra-team cooperation purpose.
        I guess we are not alone working that way in the Jira community

        1. Apr 13, 2007

          Henri Yandell says:

          See the 2.2 release Vincent. Future releases is now supported, and the embedded...

          See the 2.2 release Vincent.

          Future releases is now supported, and the embedded HTML issue should be taken care of.

          1. Apr 19, 2007

            Vincent Eggen says:

            Installed and quickly tried them: great job! I've briefly demoed them to some ...

            Installed and quickly tried them: great job!

            I've briefly demoed them to some selected users and their feedback is very positive. You're filling an unexpected gap here.

            I did only a few tests but I noticed some strange behaviours about the release table portlet, depending on the kind a config are passed to it. I'll dig in deeper and come back to you with a more precise feedback.

            The release status is very promising and despite the basic approach regarding the velocity calculation, it's already one of the most expected new feature by our PMs. From my perspective, the capacity to remove by configuration the subtasks from the portlet's scope is the next great improvement.

            I've also noticed a regression in the release status portlet: the portlet url (the one in the top left of the portlet in the dashboard configure mode) doesn't work. I don't know for other Jira/Confuence users, but here, most of our people are using this url to make anonymous access to some specific portlets in order to share them. The portlet url is often embedded in shared wiki pages or documents. It was working with the previous version. Did the anonymous access changed something about this ?

            In any case, many thanks for your velocity and your capacity to integrate people feedback in your efforts. I'll keep you in touch with my tests results.

            1. Apr 19, 2007

              Henri Yandell says:

              I can replicate the regression - it only seems to be a problem for the portlet w...

              I can replicate the regression - it only seems to be a problem for the portlet when there is only the one version set; which is a relief as the next/previous arrows use that same url I'm getting a NPE in the logs, so it shouldn't be a tricky one to fix. I'll also get working on the TreeMap bug too. Thanks for finding both of those.

              The subtask feature worries me speedwise; currently I use the getSearchCount (or whatever the method name is) feature of the API. Basically getting the values from the indexes. To ignore subtasks I think I'll have to walk all the issues and that could suck mightily for speed. Still - it's on the drawing board, as I'd like to have the opposite of ignore subtask parents. Just a chunk of code. Same kind of thing is needed for my current feature attempt, to allow an unversioned version.

              Hopefully I'll have a bugfix release out soon.

          2. Apr 19, 2007

            Vincent Eggen says:

            Ok, I found an issue with the Release table: when multiple jira projects have re...

            Ok, I found an issue with the Release table: when multiple jira projects have releases with a similar release date, the release table only shows one of these releases.

            I guess it's due to the use of the release date as the key of the TreeMap collection of versions

            1. Apr 19, 2007

              Henri Yandell says:

              This should be fixed in today's 2.3 release, as should the portlet url giving a ...

              This should be fixed in today's 2.3 release, as should the portlet url giving a white screen and a couple of other bugs.

  5. Apr 04, 2007

    Adam Bugaj says:

    Hellp me What i shoul put in field   Version ID: the name of Reales or...

    Hellp me What i shoul put in field   Version ID: the name of Reales or whta?

    1. Apr 05, 2007

      Henri Yandell says:

      The Version ID. I've tended to rely on typed in IDs rather than trying to have a...

      The Version ID. I've tended to rely on typed in IDs rather than trying to have a drop-down of all versions in the JIRA install. The easiest way to find one is to goto an issue in that version and mouse over the Fix Version or Affects Version link.

      If it's Fix Version, then you'll see 'fixFor=10010' or somesuch in the URL. 10010 is your ID. If it's Affects Version then you'll see 'version=10010'.

      Hope that helps.

  6. Apr 16, 2007

    hernan guelman says:

    I know the answer will be no... but: will this work with JIRA version 3.6.2-#15...

    I know the answer will be no... but:

    will this work with JIRA version 3.6.2-#156 ?

    1. Apr 16, 2007

      Henri Yandell says:

      I think there's a good chance it will. I put 3.7.3 simply because that and 3.8 ...

      I think there's a good chance it will.

      I put 3.7.3 simply because that and 3.8 are the JIRA versions that I develop/test on.

      My plugins won't tend to work before 3.5 (I think) because I use the downloadable resources feature for various images, but 3.6+ is probably good. If you get the chance to try, I suspect other readers of this page would love to know.

      1. Apr 18, 2007

        hernan guelman says:

        Well, I tried. I don't think my news are good. When I try to add the portlet, I ...

        Well, I tried. I don't think my news are good. When I try to add the portlet, I get the not so happy face below. The good news, removing the portlet makes everything ok again... The Releases tab works...

        System Error


        Cause:
        java.lang.NoSuchMethodError: com.atlassian.jira.project.ProjectManager.getProjectObj(Ljava/lang/Long;)Lcom/atlassian/jira/project/Project;

        Stack Trace: [hide]java.lang.NoSuchMethodError: com.atlassian.jira.project.ProjectManager.getProjectObj(Ljava/lang/Long;)Lcom/atlassian/jira/project/Project;
        at com.sourcelabs.jira.plugin.portlet.releases.ReleaseStatusPortlet.getVelocityParams(ReleaseStatusPortlet.java:146)
        at com.atlassian.jira.portal.PortletImpl.getViewHtml(PortletImpl.java:64)
        at org.apache.jsp.secure.views.dashboard_jsp._jspService(org.apache.jsp.secure.views.dashboard_jsp:1133)
        ...Build Information:
        Uptime: N/A
        Edition: Standard
        Version: 3.6.2
        Build Number: 156
        Atlassian Partner: null

        Server Information:
        Application Server: Apache Tomcat/5.5.9
        Servlet Version: 2.4
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)

  7. Apr 17, 2007

    ian says:

    Great plugin - thanks Henri. Would it be possible to have the option to display...

    Great plugin - thanks Henri.

    Would it be possible to have the option to display the Release Status Plug-in information within the Release Table?

    This would given a great overview of release activity past, future & overdue

    1. Apr 18, 2007

      Henri Yandell says:

      Quite tricky I think Ian, if I'm understanding what you're suggesting. ie) some ...

      Quite tricky I think Ian, if I'm understanding what you're suggesting. ie) some kind of hidden div in the release table that you click on and it shows the release status.

      It would be nice to provide a way for multiple release status's to live in one space - ie) Maybe a Projects drop down that lets you choose a project to do an auto-configure on. That would be a nice thing for JIRAs with lots of projects on-going.

      Maybe with a random default project.

  8. Apr 24, 2007

    ian says:

    I was thinking that the option would be in the Portlet Settings, e.g. Version De...

    I was thinking that the option would be in the Portlet Settings,
    e.g. Version Detail: Summary or Detail

    When Summary is selected, the table renders as it does now.

    When Detail is selected, the table row which contains the version info (i.e. name, project, date) is replaced with the section from the status portlet (see image)

    1. Jul 04, 2007

      Henri Yandell says:

      Recorded as: https://jira.sourcelabs.org/jira/browse/RSP-52 Though this seems q...

      Recorded as: https://jira.sourcelabs.org/jira/browse/RSP-52

      Though this seems quite tricky to do without lots of duplication.

  9. May 29, 2007

    Juha Sadeharju says:

    When using this plugin via jiraportlet in Confluence 2.5 and clicking an arrow t...

    When using this plugin via jiraportlet in Confluence 2.5 and clicking an arrow to display next version, it tries to execute javascript from the JIRA url, i.e. http://jira.server.com/jira/secure/javascript:getPortlet(..) resulting in an 404 error.

    Looking at HTML is says a href="http://jira.server.com/jira/secure/javascript:getPortlet(...)"

    I suppose correct URL would be a href="javascript:getPortlet(....)"

    1. Jul 04, 2007

      Henri Yandell says:

      Recorded as: https://jira.sourcelabs.org/jira/browse/RSP-51

      Recorded as: https://jira.sourcelabs.org/jira/browse/RSP-51

  10. Jul 12, 2007

    Mark Derricutt says:

    I noticed after upgrading to JIRA 3.10 that the portlet throws exceptions and ma...

    I noticed after upgrading to JIRA 3.10 that the portlet throws exceptions and makes a right mess of JIRA :(  I don't have the stacktrace handy off hand but will comment again in the morning with it.  Is there a 3.10 compatible build on the cards shortly?

    1. Jul 12, 2007

      Henri Yandell says:

      I've nothing planned, but as I need to upgrade various JIRA's I admin to 3.10, I...

      I've nothing planned, but as I need to upgrade various JIRA's I admin to 3.10, I'm going to need to look at this asap.

      Could you raise it in the issue tracker?

      https://jira.sourcelabs.org/jira/secure/Dashboard.jspa&nbsp;

      1. Jul 27, 2007

        Vincent Eggen says:

        Exception confirmed on Jira V3.10. Affecting version 2.3 of the portlets. I had ...

        Exception confirmed on Jira V3.10. Affecting version 2.3 of the portlets.
        I had to disable the Release Status and the Release Table portlets.
        The Releases Project Tab works fine.

        Any fixing date known already ?

        Vince

        1. Jul 29, 2007

          Henri Yandell says:

          The newly released 2.3.1 should fix this (and another small bug that happened to...

          The newly released 2.3.1 should fix this (and another small bug that happened to be in SVN).

          1. Jul 29, 2007

            Vincent Eggen says:

            Great. I wasn't expected that much reactivity. Many thanks. Vince

            Great. I wasn't expected that much reactivity.
            Many thanks.

            Vince

          2. Jul 30, 2007

            Vincent Eggen says:

            Correction confirmed on 3.10. Many thanks. BTW, I also noticed a set of error m...

            Correction confirmed on 3.10. Many thanks.

            BTW, I also noticed a set of error messages coming from the release table portlet:

            2007-07-30 09:08:44,687 http-8080-Processor22 ERROR [velocity] Left side ($versionManager.isVersionOverDue($version)) of
 '==' operation has null value. If a reference, it may not be in the context. Operation not possible. templates/releases
portlet/latestreleases.vm [line 4, column 59]

            Doesn't look blocking.
            Any idea ?

            Vince

  11. Aug 02, 2007

    J. Russell Noseworthy says:

    I get an exception from Jira 3.10 when I use any version other than an integer w...

    I get an exception from Jira 3.10 when I use any version other than an integer with the 2.3.1 version of the Release Status portlet. E.g., our releases are named things like "1.0.55" or "dingo". Releases like that raise exceptions like this:

    java.lang.NumberFormatException: For input string: "1.0.55"
    at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
    at java.lang.Long.parseLong(Long.java:412)
    at java.lang.Long.valueOf(Long.java:518)
    at com.sourcelabs.jira.plugin.portlet.releases.ReleaseStatusPortlet.getVelocityParams(ReleaseStatusPortlet.java:183)
    at com.atlassian.jira.portal.PortletImpl.getViewHtml(PortletImpl.java:68)
    at com.atlassian.jira.web.portlet.bean.PortletRenderer.getNormalHtml(PortletRenderer.java:83)
    at com.atlassian.jira.web.portlet.bean.PortletRenderer.renderPortlet(PortletRenderer.java:61)

    The only thing I could get to not raise an exception was simple integers. Am I doing something wrong or is this in fact a bug?

    Also, the Release Tables portlet gives these errors in the log when I use it:

    2007-08-02 17:41:18,648 TP-Processor29 ERROR [velocity] Left side ($versionManager.isVersionOverDue($version)) of '==' operation has null value. If a reference, it may not be in the context. Operation not possible. templates/releasesportlet/latestreleases.vm [line 4, column 59]

    1. Aug 02, 2007

      Henri Yandell says:

      Use the  version id rather than the version name. If you mouse over a link ...

      Use the  version id rather than the version name. If you mouse over a link for the version, you'll see a 5-digit number.

      1. Aug 03, 2007

        J. Russell Noseworthy says:

        Hmmm ... when I mouse over the version, I only see the text for the description ...

        Hmmm ... when I mouse over the version, I only see the text for the description of the version.

        Separate question: Any ideas about the other problem I'm having with the latest releases portlet?

        007-08-02 17:41:18,648 TP-Processor29 ERROR [velocity] Left side ($versionManager.isVersionOverDue($version)) of '==' operation has null value. If a reference, it may not be in the context. Operation not possible. templates/releasesportlet/latestreleases.vm [line 4, column 59]

        1. Aug 03, 2007

          Henri Yandell says:

          Yep, I was battling with this last night. In JIRA 3.10, the macro for showing a...

          Yep, I was battling with this last night.

          In JIRA 3.10, the macro for showing a date (handling it being red when overdue etc) was changed in a non-backwards compatible way. I've got this fixed in trunk, but was going to jam a few more features in before a 2.4 release. With the weekend near - would a 2.4 release ASAP help you, or just one by Monday?

          1. Aug 03, 2007

            Henri Yandell says:

            I just tested this directly, and it's not fixed even with the latest code. ...

            I just tested this directly, and it's not fixed even with the latest code.  Looking at it a bit deeper - it's because it's with 'latest releases' and not the one I fixed this with (release status). So... easy fix, just needs to be done.

            Could you raise this in JIRA?

            1. Aug 03, 2007

              J. Russell Noseworthy says:

              done.  RSP-62

              done.  RSP-62

              1. Oct 19, 2007

                Sergey Churikov says:

                Today I've updated Jira version from 3.9 up to 3.11 and decided to install this ...

                Today I've updated Jira version from 3.9 up to 3.11 and decided to install this pluging. In the catalina.out file I have this error now:

                ERROR [velocity] Left side ($versionManager.isVersionOverDue($version)) of '==' operation has null value. If a reference, it may not be in the context. Operation not possible. templates/releases-projecttab.vm [line 4, column 59]

                 As I understand this error should be solved with 3.10 Jira version but it seems it is not so. Any ideas?

                1. Oct 30, 2007

                  Henri Yandell says:

                  Yep, confirmed. Thanks Sergey. Looking into it. https://jira.sourcelabs.org/ji...

                  Yep, confirmed. Thanks Sergey. Looking into it.

                  https://jira.sourcelabs.org/jira/browse/RSP-70

                2. Oct 31, 2007

                  Owen Carter says:

                  I thought I'd confirm that this also happens in our environment, plugin v2.4 and...

                  I thought I'd confirm that this also happens in our environment, plugin v2.4 and Jira 3.10.2, so yes, it's there on 3.10 too..

      2. Aug 03, 2007

        J. Russell Noseworthy says:

        I was able to discover the version ids, but it wasn't easy.  I grep-ed thro...

        I was able to discover the version ids, but it wasn't easy.  I grep-ed through an XML dump for "Version id="

        1. Aug 03, 2007

          Henri Yandell says:

          Ack - I'm sorry. I totally didn't think of the default state of browsers. I alw...

          Ack - I'm sorry. I totally didn't think of the default state of browsers.

          I always turn on the Status bar at the bottom so that when I mouse over links I see the url at the bottom of the page. It's how browsers used to be, so I forget that it's not the default now.

          I'm sorry to put you through all that, I'll update the website to mention that. 

  12. Aug 03, 2007

    J. Russell Noseworthy says:

    I get an exception with version 2.3.1 and jira 3.10 with some projects:  2...

    I get an exception with version 2.3.1 and jira 3.10 with some projects:

     2007-08-03 12:15:44,644 TP-Processor16 WARN [velocity] org.apache.velocity.runtime.exception.ReferenceException: reference : template = templates/releasesportlet/releasestatus.vm [line 1,column 1] : $version.description is not a valid reference.
            at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:277)
            at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
            at org.apache.velocity.runtime.parser.node.ASTStringLiteral.value(ASTStringLiteral.java:145)
            at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:144)
            at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
            at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
            at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55)
            at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
            at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:89)
            at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55)
            at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:70)
            at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
            at org.apache.velocity.Template.merge(Template.java:256)
            at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:450)
            at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:76)
            at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:60)
            at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:55)
            at com.atlassian.jira.plugin.JiraResourcedModuleDescriptor.getHtml(JiraResourcedModuleDescriptor.java:90)
            at com.atlassian.jira.portal.PortletImpl.getViewHtml(PortletImpl.java:69)
            at com.atlassian.jira.web.portlet.bean.PortletRenderer.getNormalHtml(PortletRenderer.java:83)
            at com.atlassian.jira.web.portlet.bean.PortletRenderer.renderPortlet(PortletRenderer.java:61)
            at org.apache.jsp.secure.views.runportlet_jsp._jspService(org.apache.jsp.secure.views.runportlet_jsp:104)
            at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)

    1. Aug 03, 2007

      Henri Yandell says:

      Not one I can replicate - versions without a description seem to happily just no...

      Not one I can replicate - versions without a description seem to happily just not show anything (they have an empty title=""). 

      Could you open an issue in JIRA for this? The one thing I can do is change the $version.description to $!version.description so it doesn't care when there's no description. Your database might be older than mine, or a different way of making a version or something and so your version descriptions are null while mine are empty strings. The ! makes null be treated as an empty string, so doesn't really hurt and might fix this for you.

      1. Aug 03, 2007

        J. Russell Noseworthy says:

        Done.  RSP-63

        Done.  RSP-63

        1. Aug 04, 2007

          Henri Yandell says:

          Hopefully the newly released 2.4 will take care of the issues you've reported. P...

          Hopefully the newly released 2.4 will take care of the issues you've reported. Please let me know if they don't.

          Thanks for all the feedback. 

  13. Sep 19, 2007

    Colin Goudie says:

    I've embedded the JIRA Release Status Portlet into a Confluence page using the {...

    I've embedded the JIRA Release Status Portlet into a Confluence page using the
    {jiraportlet} macro. However, it looks kind of ugly. I'm guessing some of the styles are missing. Is there a way to embed the required styles to make it look more like it does in JIRA? If that makes sense.
    Thanks

    1. Sep 20, 2007

      Henri Yandell says:

      I guess the problem is that the JIRA CSS is not available; generally I use that ...

      I guess the problem is that the JIRA CSS is not available; generally I use that so it fits naturally into JIRA.

      Are you able to add a line to include the CSS into the confluence page? I'm not much of a Confluence user so pretty clueless about it.

  14. Sep 25, 2007

    Gert-Jan Bartelds says:

    Hello, I have been successfully using the 2.4 version with JIRA 3.10.2 . I am no...

    Hello, I have been successfully using the 2.4 version with JIRA 3.10.2 . I am now trying to run it with the new JIRA 3.11 and unfortunately the plugin reports an error. For your information, here is the info from the logfile. It looks as if it's the same error which occurs in the current user portlet with 3.11

    Hope this helps, Gert-Jan

    2007-09-25 14:26:13,132 main ERROR [atlassian.plugin.parsers.XmlDescriptorParser] There were problems loading the module 'portlet'. The module and its plugin have been disabled.
    2007-09-25 14:26:13,132 main ERROR [atlassian.plugin.parsers.XmlDescriptorParser] There was a problem loading the descriptor for module 'portlet' in plugin 'Releases Plugin'.
     java.lang.VerifyError: Cannot inherit from final class
    com.atlassian.plugin.PluginParseException: java.lang.VerifyError: Cannot inherit from final class
        at com.atlassian.plugin.descriptors.AbstractModuleDescriptor.init(AbstractModuleDescriptor.java:77)
        at com.atlassian.jira.plugin.JiraResourcedModuleDescriptor.init(JiraResourcedModuleDescriptor.java:45)
        at com.atlassian.jira.plugin.ConfigurableModuleDescriptor.init(ConfigurableModuleDescriptor.java:33)
        at com.atlassian.jira.plugin.portlet.PortletModuleDescriptor.init(PortletModuleDescriptor.java:46)
        at com.atlassian.plugin.parsers.XmlDescriptorParser.createModuleDescriptor(XmlDescriptorParser.java:147)
        at com.atlassian.plugin.parsers.XmlDescriptorParser.configurePlugin(XmlDescriptorParser.java:85)
        at com.atlassian.plugin.loaders.SinglePluginLoader.loadPlugin(SinglePluginLoader.java:86)
        at com.atlassian.plugin.loaders.SinglePluginLoader.loadAllPlugins(SinglePluginLoader.java:50)
        at com.atlassian.plugin.loaders.ClassPathPluginLoader.loadClassPathPlugins(ClassPathPluginLoader.java:50)
        at com.atlassian.plugin.loaders.ClassPathPluginLoader.loadAllPlugins(ClassPathPluginLoader.java:63)
        at com.atlassian.plugin.DefaultPluginManager.init(DefaultPluginManager.java:70)
        at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:28)
        at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:356)
        at com.atlassian.jira.ComponentManager.start(ComponentManager.java:334)
        at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:31)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
        at org.apache.catalina.core.StandardService.start(StandardService.java:450)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
    Caused by: java.lang.VerifyError: Cannot inherit from final class
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
        at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1815)
        at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:869)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1322)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1201)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        at java.lang.Class.getDeclaredConstructors0(Native Method)
        at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
        at java.lang.Class.getConstructor0(Class.java:2671)
        at java.lang.Class.getConstructor(Class.java:1629)
        at com.atlassian.plugin.descriptors.AbstractModuleDescriptor.init(AbstractModuleDescriptor.java:51)
        ... 29 more
    2007-09-25 14:26:13,132 main ERROR [atlassian.plugin.parsers.XmlDescriptorParser] There were errors loading the plugin 'Releases Plugin'. The plugin has been disabled.

    1. Sep 25, 2007

      Henri Yandell says:

      Thanks Gert, Recorded as https://jira.sourcelabs.org/jira/browse/RSP-68.

      Thanks Gert,

      Recorded as https://jira.sourcelabs.org/jira/browse/RSP-68.

      1. Sep 28, 2007

        Henri Yandell says:

        This has now been released as 2.4.1. Note that this plugin is now 3.11+ spec...

        This has now been released as 2.4.1. Note that this plugin is now 3.11+ specific - on older versions of JIRA the progress bar colour will not display.

  15. Jan 15, 2008

    Carman Okon says:

    Hi Henri, Great Plug-in, How do I get it to work with only one version. When I ...

    Hi Henri,

    Great Plug-in, How do I get it to work with only one version. When I set up the plug in on my dashboard and select a project with one or no versions, the plug in does not work. Any help would surely be appreciated.

    1. Jan 28, 2008

      Henri Yandell says:

      Sorry for letting 2 weeks fly by. If a project has no versions, then it doesn't...

      Sorry for letting 2 weeks fly by.

      If a project has no versions, then it doesn't show anything. That's largely by intent to deal with noise on the random option. I can confirm that if you have one version it still doesn't show anything - not sure when that got introduced, I don't think it's always been that way. I've created a JIRA issue to track that further:

      https://jira.sourcelabs.org/jira/browse/RSP-71

      1. Jan 31, 2008

        Henri Yandell says:

        2.4.2 is released, which fixes the one-version bug raised in RSP-71. I've recor...

        2.4.2 is released, which fixes the one-version bug raised in RSP-71.

        I've recorded the no-version problem as an enhancement in https://jira.sourcelabs.org/jira/browse/RSP-72

  16. Aug 08, 2008

    James Levinson says:

    Thank you so much for your work on this Plugin. It think it will prove to be ver...

    Thank you so much for your work on this Plugin. It think it will prove to be very useful for us. We are on Enterprise Edition, Version: 3.12.2-#300.

    I am a bit confused by point 3 above which discusses the third portlet, which is accesible via the project page. I do not see a Subversion Commits tab. We use the jira-fisheye plugin and I do see a fisheye tab. I see the following tabs:

    Select: Open Issues Road Map Change Log Popular Issues Releases Versions FishEye  

    I have some sort of internal problem that is generating an error on the fisheye tab "Error communicating with FishEye: java.io.IOException: revision not found: 65710", so I cannot see what is on it.

    My question is, what is supposed to show up on the fisheye (or Subversion Commits) tab ? Is it all commits for the project or is it broken down by version? I ask this because it would be great if there was a way to generate a changelist of files for a specific fixversion? And, this portlet seems like the ideal place for this activity. Perhaps, this exists already and I am not seeing it ? If not, it would be a worthy enhancement.

    1. Aug 09, 2008

      Henri Yandell says:

      I'm not sure if I'm the right person for that question. The subversion and fishe...

      I'm not sure if I'm the right person for that question. The subversion and fisheye plugins are different ones that I believe Atlassian provide. Both do the same thing, integrating with a source code repository (fisheye can do multiple types while subversion does subversion). It sounds like you need to dig into their docs regarding problems with the FishEye configuration.

  17. Sep 29, 2008

    Gael CROVA says:

    Hi, I tried the last version (2.4.2) on Jira 3.13 and it seems to work but I go...

    Hi,

    I tried the last version (2.4.2) on Jira 3.13 and it seems to work but I got the following error in log files running the 'project tab panel':

    http-9007-Processor20 ERROR [velocity] Left side ($versionManager.isVersionOverDue($version)) of '==' operation has null value. If a reference, it may not be in the context. Operation not possible. templates/releases-projecttab.vm [line 4, column 59]

    Could you provide a new plugin version for Jira 3.13 ?

     Thanks in advance

     Gael

    1. Nov 04, 2008

      Henri Yandell says:

      Issue fixed. It's a pre-existing issue from 3.10 (iirc) that's been there for a ...

      Issue fixed. It's a pre-existing issue from 3.10 (iirc) that's been there for a while and only affects whether the date is shown in red or not.

  18. Oct 29, 2008

    Sergiy Lizenko says:

    We have the same problem. Very want  to have upgrade too.

    We have the same problem.
    Very want  to have upgrade too.