This server will be upgraded at 6:30am GMT (4:30pm Sydney time). There will be a brief outage.

JIRA Suite Utilities

Added by Gustavo Martin, last edited by Jean-Baptiste Catté on Apr 21, 2008  (view change)
Name JIRA Suite Utilities
Version 0.6.3
Author(s) Gustavo Martin
Homepage http://code.google.com/p/jira-suite-utilities/
Price Free
License BSD
IssueTracking http://code.google.com/p/jira-suite-utilities/issues/list
Download http://code.google.com/p/jira-suite-utilities/downloads/list
Mailing list http://groups.google.com/group/jira-suite-utilities-discuss
JDK 1.5 or upper

Description/Features

This pluging is divided in two parts. First, a set of conditions and validations to personalize workflow of JIRA. And second, a Issue Tab Panel, which shows information about the execution of each transition. A little addition - custom fields for specifying Google Maps location.

  • Custom Fields
    - Location Text: custom field for specifying address in free form text. Location will be shown as inline Google Map.
    - Location Select: custom field for selecting address from predefined list. Location will be shown as inline Google Map.
  • Workflow Conditions:
    - User Is In Any Groups: which allows to only execute a transition, if the user belongs to one of the selected groups. By means of this condition, it will not be necessary to edit the xml of workflow to allow that the user belongs to a group or another one.
    - Value Field: it allows to execute the transition on the basis of the value of a field.
  • Workflow Validators:
    - Fields Required: it allows to select a set of fields, to do required them during the execution of a transition.
    - Date Compare: allowing to choose single type fields it dates, to compare the date of a field against the one of another one.
    - Window Dates: it establishes that the date of a field, must be between two dates. Which are determined by the value of another field and a window of time, in days.
  • Post functions:
    - Copy Value From Other Field: this function copies the value of one field to another.
    - Update Issue Custom Field: it updates an issue custom field to a given value.
    - Clear Field Value: this function used for cleaning field value.
  • Issue Tab Panel:
    - Transitions Summary Tab Panel: It shows the total duration of each executed transition, whichever times was executed, who and when was the last time that executed it.

Detailed description - http://code.google.com/p/jira-suite-utilities/wiki/DetailedDescription

Version compatibility

Tested JIRA/plugin combinations – please note your own experiences in the comments.

JIRA Version Plugin version
3.12.x 0.6.3
3.11.x 0.6.3
3.10.x 0.6
3.9.x 0.6
3.8.x 0.6
3.7.x 0.6-EA4
3.6.2 0.5.0

Upgrading

When you upgrade from 0.6.1 to 0.6.3+ you may receive an error such as:

Error

Could not load class 'com.atlassian.jira.plugin.workflow.function.UpdateIssueCustomFieldPostFunction'

This occurs because the Jira Suite classes have been renamed and Jira stores the names of the classes in the workflow.

You need to re-create all custom field Post Functions. If you don't want to do this by hand, you can apply the following strategy:

  1. Export the failing workflow as XML
  2. Replace "com.atlassian.jira.plugin.workflow.function" with "com.googlecode.jsu.workflow.function"
  3. Create a new workflow and a new workflow scheme to replace the failing workflow, and modify the projects to use the new scheme

Labels

 

Comments (170)

 

  1. Apr 21, 2006

    Benjamin Joguet says:

    I get a problem with the "Fields required" Validator. When I click on the "Add" ...

    I get a problem with the "Fields required" Validator. When I click on the "Add" button I get a javascript error and nothing appears on the "required fields" list. I use IE6 on WinXP.

    1. Apr 26, 2006

      Benjamin Joguet says:

      Retranscripted Javascript error :  Ligne : 786 Car : 21 Erreur : Argument n...

      Retranscripted Javascript error : 

      Ligne : 786
      Car : 21
      Erreur : Argument non valide
      Code : 0
      URL : http://serveur:8080/secure/admin/workflows/AddWorkflowTransitionValidatorParams\!
       default.jspa?
       workflowName=Workflow+FEA+Evol1&workflowStep=1&workflowTransition=11&pluginModuleKey=com.atlassian.pluginjirasuite%
       3AfieldsRequired-validator

    2. Sep 25, 2006

      Tobias Rodenbach says:

      I get the same error when using Internet Explorer 6.0, but in Firefox 1.5.0.7 it...

      I get the same error when using Internet Explorer 6.0, but in Firefox 1.5.0.7 it works.
      HTH

  2. May 18, 2006

    Neil Arrowsmith says:

    Which versions of Jira will this plugin work with? We're using 3.2.2. currently,...

    Which versions of Jira will this plugin work with? We're using 3.2.2. currently, and the field validation would be very useful.

  3. May 22, 2006

    Christi Austin says:

    I also get an error on page when performing the below. Nothing appears in the ri...

    I also get an error on page when performing the below. Nothing appears in the right list.

    You must press the button "Add >>", that this underneath the left list. ( The selected items appear into the right list )

    Is there a trick to this? The field required validator is exactly what I have been looking for.

    1. Oct 06, 2006

      Michael Dreier says:

      Hi Christi, we have the same problem with the usage of the field required valida...

      Hi Christi,

      we have the same problem with the usage of the field required validator. Do you have a solution?

      Cheers Michael

  4. May 23, 2006

    Bettina Zucker says:

    Hello Gustavo, I'm using Jira enterprise(rel 3.5.1) and I have defined some non ...

    Hello Gustavo,

    I'm using Jira enterprise(rel 3.5.1) and I have defined some non default field configurations.

    I noticed your Required Fields Validator does not work with such field configurations, so I had to modify the code somewhat.  How to do it is explained in the Jira DEV Forum thread:

    http://forums.atlassian.com/thread.jspa?threadID=11362

    Would you be interested in the change? If yes, I can upload the source and the .jar here as attachment.

    Cheers

    Bettina Zucker 

    1. Jun 12, 2006

      Bettina Zucker says:

      Hello Gustavo, since another user had the same problem with non default field co...

      Hello Gustavo,

      since another user had the same problem with non default field configurations, I added my modified version to the attachments.
      I tested it only with my version of Jira (3.5.1). I don't know if this plugin works with the current Jira version 3.6.x.
      I attached the sources also, so the changes are easily seen by checking the 4 .java files with modification date in may 06.

      Cheers

      Bettina 

  5. May 23, 2006

    Christi Austin says:

    Hi Gustavo, I am using Jira Enterprise 3.6 and would like to know if the  "...

    Hi Gustavo,

    I am using Jira Enterprise 3.6 and would like to know if the  "Fields required" Validator will work with this version.

    When I click on the "Add" button nothing appears on the "required fields" list.

    Thanks,

    Christi 

  6. Jun 02, 2006

    Dion Adamy says:

    Yes, the fields required validator is exactly what I'm looking for as well....

    Yes, the fields required validator is exactly what I'm looking for as well. I'll keep checking daily for an updated .jar!

  7. Jun 21, 2006

    Gustavo Martin says:

    I request excuses by the delay in responding its questions. This plugin I do it ...

    I request excuses by the delay in responding its questions. This plugin I do it in my free time. And at the moment, I do not have the sufficient one as to dedicate to him...
    Coming soon it will have new features, and fix the issues commented avobe.

    Greetings.

  8. Jul 26, 2006

    Reid Sayre says:

    The "required fields" validator is exactly what we have been looking for. We hav...

    The "required fields" validator is exactly what we have been looking for. We have installed it on 3.6.2 and works fine.

    We could really use "Time Tracking" (either "original estimate" or "remaining estimate" depending on what's displayed) to be a required field on some transitions. Do you have any idea when this might be available?

    Thanks for a great plug-in!!

  9. Jul 31, 2006

    Remon van Gijn says:

    I was so hoping this would fix our need to have the fixversion a required field ...

    I was so hoping this would fix our need to have the fix-version a required field only when migrating from OPEN to resolved. But we also have the ADD button problem. Same issue as above, and listed in this comment: http://confluence.atlassian.com/display/JIRAEXT/JIRA+Suite+Utilities?focusedCommentId=171482#comment-171482

    Hope you can fix this, not able to add the selected entries from the left to the right list.

  10. Aug 17, 2006

    jpp says:

    Hi,  I have this "Field Required" issue too. We are using JIRA 3.6.1 Enterp...

    Hi,

     I have this "Field Required" issue too. We are using JIRA 3.6.1 Enterprise.

     It gives following error:

    Line: 846Char: 21Error: Invalid argument.Code: 0URL: https://......./secure/admin/workflows/AddWorkflowTransitionParams!default.jspa?workflowName=W1&workwlowStep=1&workflowTransition=4&pluginModuleKey=com.atlassian.jira.plugin.jirasuite%3AfieldsRequired-validator 

  11. Sep 12, 2006

    yuval yeret says:

    Fields required is a very useful (I would say essential) addon to JIRA  I'm...

    Fields required is a very useful (I would say essential) addon to JIRA

     I'm using Jira 3.6.3 Enterprise, and was able to successfully apply a fields required validator to some transitions in my custom workflow.

    when trying to do a specific transition, I'm encountering

    1. Sep 12, 2006

      yuval yeret says:

      somehow the comment was cut. anyhow the error is: An unknown exception occured e...

      somehow the comment was cut.

      anyhow the error is: An unknown exception occured executing Validator: com.atlassian.jira.plugin.workflow.validator.FieldsRequiredValidator: root cause: java.lang.NullPointerException

      Once it happens, I cannot do that transition for the specific issue which had the problem even if I disable the validator, or even disable the whole plugin (including restart to JIRA).

      Other issues where I didn't try the transition while the validator was enabled can do the transition fine after its disabled.

      I am using a custom field, but didn't encounter problems adding it to the validator, so it sounds like a different issue?

      1. Sep 12, 2006

        leon oosterwijk says:

        I also get the nullPointer Exception. I'm using Jira 3.6.2. currently. here is t...

        I also get the nullPointer Exception. I'm using Jira 3.6.2. currently.

        here is the full stracktrace in case it helps. I really would like to have this work because it is a great tool.

        2006-09-12 14:37:31,928 ERROR [atlassian.jira.workflow.SimpleWorkflowManager] An exception occurred
        com.opensymphony.workflow.WorkflowException: An unknown exception occured executing Validator: com.atlassian.jira.plugin.workflow.validator.FieldsRequ
        iredValidator: root cause: java.lang.NullPointerException
                at com.opensymphony.workflow.AbstractWorkflow.verifyInputs(AbstractWorkflow.java:996)
                at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1198)
                at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:533)
                at com.atlassian.jira.workflow.SimpleWorkflowManager.doWorkflowAction(SimpleWorkflowManager.java:232)
                at com.atlassian.jira.workflow.WorkflowTransitionUtilImpl.progress(WorkflowTransitionUtilImpl.java:271)
                at com.atlassian.jira.web.action.issue.CommentAssignIssue.doExecute(CommentAssignIssue.java:190)
                at webwork.action.ActionSupport.execute(ActionSupport.java:153)
                at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:58)
                at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132)
                at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:185)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:51)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119)
                at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55)
                at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:182)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at com.atlassian.seraph.filter.LoginFilter.doFilter(LoginFilter.java:177)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132)
                at com.atlassian.jira.web.filters.ProfilingAndErrorFilter.doFilter(ProfilingAndErrorFilter.java:25)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:39)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at com.atlassian.johnson.filters.JohnsonFilter.doFilter(JohnsonFilter.java:91)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at com.atlassian.jira.web.filters.gzip.GzipFilter.doFilter(GzipFilter.java:72)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
                at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
                at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
                at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
                at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
                at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
                at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
                at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
                at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
                at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
                at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
                at java.lang.Thread.run(Thread.java:534)

  12. Sep 15, 2006

    Neal Applebaum says:

    I tested this on my standalone JIRA (the required fields on transition), and it ...

    I tested this on my standalone JIRA (the required fields on transition), and it worked great. But whenI used it on my live system (also 3.6.3) , it generated this error:

    An unknown exception occured executing Validator: com.atlassian.jira.plugin.workflow.validator.FieldsRequiredValidator: root cause: java.lang.NullPointerException

    ERROR [atlassian.jira.workflow.SimpleWorkflowManager] An exception occurred
    [InvalidInputException: [Error map: [

    Unknown macro: {customfield_10130=Files Modified is required.}
    ]] [Error list: [[]]]
        at com.atlassian.jira.plugin.workflow.validator.FieldsRequiredValidator.setError(FieldsRequiredValidator.java:130)
        at com.atlassian.jira.plugin.workflow.validator.FieldsRequiredValidator.validate(FieldsRequiredValidator.java:94)
        at com.opensymphony.workflow.AbstractWorkflow.verifyInputs(AbstractWorkflow.java:985)
        at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1198)
        at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:533)
        at com.atlassian.jira.workflow.SimpleWorkflowManager.doWorkflowAction(SimpleWorkflowManager.java:243)
        at com.atlassian.jira.workflow.WorkflowTransitionUtilImpl.progress(WorkflowTransitionUtilImpl.java:271)
        at com.atlassian.jira.web.action.issue.CommentAssignIssue.doExecute(CommentAssignIssue.java:190)
        at webwork.action.ActionSupport.execute(ActionSupport.java:153)
        at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:57)
        at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132)
        at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:185)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:51)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119)
        at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55)
        at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:182)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.atlassian.seraph.filter.LoginFilter.doFilter(LoginFilter.java:181)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132)
        at com.atlassian.jira.web.filters.ProfilingAndErrorFilter.doFilter(ProfilingAndErrorFilter.java:35)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:39)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.atlassian.johnson.filters.JohnsonFilter.doFilter(JohnsonFilter.java:91)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.atlassian.jira.web.filters.gzip.GzipFilter.doFilter(GzipFilter.java:72)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:534)

  13. Sep 29, 2006

    Irene Chan says:

    We are in the process of testing the upgrade from 3.5.3 to 3.6.5. When I go to a...

    We are in the process of testing the upgrade from 3.5.3 to 3.6.5.

    When I go to add a validator and select the option "Window Dates", after I add the condition, it says the message:  "It must fulfill that is within the days from ."  when I select the validator "Window Dates".

    When I add a condition using the option "Value Field", I get the message below after I add the condition.  Is there a known bug or incompatibility of this plug-in for version 3.6.5? 
    Type: class
    Class: com.atlassian.jira.plugin.workflow.condition.ValueFieldCondition

    Do you know how this option is supposed to be used? 
    Thanks
    Irene

  14. Sep 30, 2006

    Carl Jones says:

    running 3.5 Got this when I tried to make component and affects versions require...

    running 3.5

    Got this when I tried to make component and affects versions required on the create screen.  Took it off the create screen and problem went away; works for all other screens.  Thanks!  -carl

    Errors
    Error creating issue: com.atlassian.jira.workflow.WorkflowException: com.opensymphony.workflow.WorkflowException: An unknown exception occured executing Validator: com.atlassian.jira.plugin.workflow.validator.FieldsRequiredValidator: root cause: java.lang.NullPointerException

    1. Oct 06, 2006

      Neal Applebaum says:

      Carl, If you want those fields required right from issue creation, why don't you...

      Carl,

      If you want those fields required right from issue creation, why don't you just make them required in JIRA (which means they will be required at all stages of the issue)? Is there a use case that, after creation, they can blank out those fields? 

      1. Oct 06, 2006

        Remon van Gijn says:

        Niel, At creation of the issue the definition of the fixversion mostly is "The v...

        Niel,

        At creation of the issue the definition of the fix-version mostly is "The version where the issue needs to be resolved on"

        In allot of organistations (allike mine for instance) it is not permitted to assign a fix version initially, as this is done by the teamleader of the product, to enable a planning workflow.

        But later on in the life of the issue, it is not organisational allowed to resolve the issue by the programmer without a fix version (where the actual work is done). Without this script this cannot be enforced automatically.

  15. Nov 07, 2006

    Yudit Barmatz says:

    Hi, It seems that the order of lines in the "Transitions Summary" Tab is not log...

    Hi,
    It seems that the order of lines in the "Transitions Summary" Tab is not logical ...
    It isn't sorted by date, and changing the sort direction with arrow doesn't help.
    - I have a problem attaching the screen shot, but the exact order of 'Last Execution Date' is :

    28/Sep/06 09:56 AM
    28/Sep/06 09:59 AM
    28/Sep/06 09:55 AM
    28/Sep/06 10:38 AM
    28/Sep/06 10:36 AM 
    28/Sep/06 10:36 AM 

    Please advise,
    Thanks,
            Yudit.

    1. Nov 07, 2006

      Neal Applebaum says:

      I don't think the author's intention was to show each transition, in order. The ...

      I don't think the author's intention was to show each transition, in order. The intention was to show a summary of transitions, so that if an issue was resolved and re-opened 3 times, there would be one entry for that showing that it has been executed 3 times in total over the life of the issue.

      1. Nov 28, 2006

        Yudit Barmatz says:

        Even if the intention was just to show a summary of transitions, the fact is, th...

        Even if the intention was just to show a summary of transitions, the fact is, that the date is displayed and there is a possibility to 'Sort'.
        Indeed we can see that there is some attempt at sorting, but it seems that they have a bug in the order.

        Please fix so that this tab will be useful and meaningful.
        Thanks.

  16. Nov 07, 2006

    Pierrick says:

    Hi all, I get the same null pointer exception which is reported here

    Hi all,

    I get the same null pointer exception which is reported here http://confluence.atlassian.com/display/JIRAEXT/JIRA+Suite+Utilities?focusedCommentId=188961#comment-188961

    (it happens when I try to resolve an issue - with some required fields).

    I'm running Jira 3.6.1, is it broken with this version? Does anybody get success to make it running on 3.6.x ?

    Thanks a lot. Cheers. Pierrick.

    1. Nov 07, 2006

      Neal Applebaum says:

      I use an alternate plugin to force required fields:

      I use an alternate plugin to force required fields:
      http://confluence.atlassian.com/x/9esB

  17. Dec 05, 2006

    Alexander Weiss says:

    Is there the plan to continue this helpful plugin for JIRA 3.7? Cheers. Alexande...

    Is there the plan to continue this helpful plugin for JIRA 3.7?

    Cheers. Alexander.

  18. Dec 13, 2006

    Neal Applebaum says:

    Note: The transitions panel is incompatible with 3.7 so if you need this plugin...

    Note:

    The transitions panel is incompatible with 3.7 so if you need this plugin installed in 3.7, you will definitely have to disable the Transitions Summary Tab Panel module, or else you won't see ANY issue tabs. Hopefully the other features will still work (the ones I use seem to).

    1. Dec 20, 2006

      Michelle de Guzman says:

      Note. For those who have recently upgraded to 3.7 and have lost the ability to s...

      Note.

      For those who have recently upgraded to 3.7 and have lost the ability to see comments when viewing issues, we have been told that disabling the Fields Required module from this plugin is also required in addition to the transitions summary tab panel described by Neal above.

      Cheers,
      Michelle

      1. Jan 12, 2007

        Alex Holtz says:

        I disabled all the modules except the "Fields Required module" and it seems to w...

        I disabled all the modules except the "Fields Required module" and it seems to work without any adverse affects in 3.7.1

        The transitions summary tab is definitely busted, though.

  19. Dec 22, 2006

    Kerstin Klein says:

    This plugin does not work with Jira 3.7. If it is used, the whole tab panel in t...

    This plugin does not work with Jira 3.7. If it is used, the whole tab panel in the issue detail screen is lost.

    1. Jan 23, 2007

      Bettina Zucker says:

      As a quick workaround to the problem with tab panels, you may just remove the "t...

      As a quick workaround to the problem with tab panels, you may just remove the "transition summary" tab panel from the atlassian-plugin.xml file, unless you really need this feature. Then the usual jira tab panels appears also in 3.7.2.

      I did it, since I really need the "fields required" validator for my customized workflows, while the panel is just a "nice-to-have" for my users.

      Cheers

      Bettina Zucker 

      1. Jan 23, 2007

        Bettina Zucker says:

        Now I see this issue was already discussed in the thread above. Sorry for wastin...

        Now I see this issue was already discussed in the thread above. Sorry for wasting your time.

        Bettina 

  20. Jan 04, 2007