JIRA Suite Utilities

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.

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

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.

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 

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 

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

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.

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!!

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.

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 

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

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: [

]] [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)

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

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

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.

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.

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

Cheers. Alexander.

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).

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

Hi,
weare migrating JIRA to another host and think of upgrading at the same time (from 3.6.3).

We will not upgrade to 3.7 because of above mentioned issues, but can anybody confirm that the Jira Suite Utilities plugin works with JIRA 3.6.5?

Thanks and regards

 Tobias 

Hi,

we used the plugin in 3.6.5 without any problems. 

The transitions summary tab panel is the only samples I found to create tab panels. Any tab panel build like that stops comments showing. Is there any other sample building a tab panel?

Cheers,
Christian

We met a problem that show negative time spent on transition summary tab, the reason is Using delegator.findByAnd can't make sure that the changeGroups are ordered by created time, here is the way to fix it:

In method getStatusChanges of class com.atlassian.jira.plugin.transitionssummary.TransitionsManager, after "List changeGroups = delegator.findByAnd("ChangeGroup", params);", add following code:

Collections.sort(changeGroups, new Comparator() {

            public int compare(Object o1, Object o2) {
                GenericValue c1 = (GenericValue)o1;
                GenericValue c2 = (GenericValue)o2;
                return c1.getTimestamp("created").compareTo(c2.getTimestamp("created"));
            }});

Hi Yuen-Chi,

I think we've already reported that the Fields Required portion doesn't work. However I use the other plugin to do that, in 3.6.5, and it works OK (except for creating exceptions in the JIRA log).

Hello,

since I really need and I really like this plugin, I spent some hours and made the upgrade to jira 3.7.

I just uploaded the .jar, see above in the attachments.

It's built with the jira-development-kit-3.7.1 and shortly tested under jira 3.7.2. The transition panel does appear now.

 Cheers

Bettina Zucker 

I've tried the ValueField condition on one of our workflows. But I can't seem to configure it to use a multi check box field.

How should i format the value to compare to for a multicheckbox custom field?

Hello!

For the first time I also got the NullPointerException bug.

It was the first time I tried to use this plugin to validate a mandatory field in the create transition.

In other transitions on issues which are already existing I did never get any problems!

So I suppose the Null Pointer comes from a wrong access to the issue, which at create does not yet exist.

If I had the time I would start debugging now...  

but I have no time!!!  Maybe later!

Cheers

Bettina 

I am now using this jar file, and it works just dandy

my question is: is there a way to clear the values in the fields when the form loads? I mean whats' the point of having required fields if you're not forcing the user to enter any new information? 

that's all i want to do, force the user to enter in new information.  let me know if any one of you knows where in the source, the filling in of the stored values is done

thanks, david

It seems the Copy Value From Other Field (copyValueFromOtherField-function) post function is missing in the 0.5.2 and 0.5.3 compiled versions of the plugin.  Was this an oversight, or was there a problem getting this to work with JIRA 3.7?  I'd really like to use this workflow post function since our current workflows rely on it.

btw, say i wanted to change some of the source code, how do i recompile it and put it into the jar? 

do i need to load the entire JIRA source into my project in eclipse?  or can i just do it straight from the command line?

bonus, i figured out maven and the compiling etc of the source code, lol, seems i'm answering alot of my own questions. but, now i have a new problem...

how does the validator work? does it first post all the fields to the database, then retrieve them to see if any are null, and throws an exception if the validator fails, which then reverts to the previous data?  i'm working on the com\atlassian\jira\plugin\workflow\validator\FieldsRequiredValidator.java file file and i know i have to change line 95

instead of checking for a null Object i want it to compare the value of the field that was entered by the user, with the field that was previously in the database.

but it seems as if the FieldValue is already being pulled from the DB

[code]if(fieldValue==null && !CommonPluginUtils.isFieldHidden(issue, field)){[/code]

I have uploaded new version with fixed Nullpointer and copy function.
Everything here http://code.google.com/p/jira-suite-utilities/downloads/list

Is it possible for the "Value" field in a Value Field Condition to be the value of another field?

We have a "Review" field that is a user picker, and we want to prevent the Reporter of the issue to be the reviewer. So it would be cool if we could have a condition on that transition that looks something like this:

$(issue.reviewer) != $(issue.reporter)

But as far as I can tell, the text in the Value field is just a literal translation/comparison.

Thanks!

-MattyJ

Could some one tell me does Value field module work with multi-select list custom fields?

Bettina/Alexy,

 This doesnt work when I have a custom field that is configured for a particular issue type and is present in a screen that I use for all issue types in the project. I think the isFieldOnScreen or isFieldHidden has to be tuned further to include this condition.

Comprehensive Explanation below:

I have 2 issue types - Bug and DataIssue. Both use Resolve Screen. I have a cf that is configured for DataIssue only. The field is added to the Resolve Screen. Depending on the Issue type, whether its Bug or Data Issue it appears on the screen. In this scenario, I try to validate my cf. I get an exception in my log and I am not able to resolve when the issue type is Bug. This should not be the case as the cf has nothing to do with Bug type. I am not familiar with the jira api hierarchy and so I got stranded trying to correct it. Any help would be appreciated.

If somebody could just mention the change in the above methods, then I can do it on my own. 

Thank you,

Raghu  

Hello!

I am trying to use the post-function  Copy Value From Other Field. I define as source "Assign To" and destination an Custom Field of type "User Picker".

When i execute the transition, i get this error:

Errors

• class com.atlassian.jira.issue.customfields.impl.UserCFType passed an invalid value of type: class java.lang.String

Am i doing something wrong? is there a problem in the plugin??

Any help would be apreciated! Thanks in advanced! 

New version with new features:

Version history - http://code.google.com/p/jira-suite-utilities/wiki/VersionHistory
Download - http://code.google.com/p/jira-suite-utilities/downloads/list

Hello Alexey,

I just have tested the new version 0.6-EA1 of the plugin with jira 3.8.1.

I still get a problem with the transition history.

Sometimes I get a null pointer, so the transition history disappears.

I get an error message:

"An unknown error occurred - actions == null. Please see logs for more details."

I know why this is happening:

Some time ago I defined a custom field named "Status", which was a status imported from another database.

The changeitems entries look like this:

| ID	| groupid| FIELDTYPE	| FIELD	| OLDVALUE	| OLDSTRING	| NEWVALUE	| NEWSTRING	|
|  89020| 51557	| jira		| status| 10007		| Rejected	| 10009		| Closed-Rej	|
| 135571| 70354	| custom	| Status| NULL		| open		| NULL		| resolved	|

where the first row is a normal jira status entry, the second my custom Status.

Here you can see, when the Transitions Manager gets my custom line, the oldvalue is NULL, so the null pointer error happens. 

I renamed the custom field when I noticed the problem, but the oldvalue field in the changeitems was not renamed.

I cannot access directly the database, because I'm only jira admin, the db is administrated quite strictly by our IT.

So the only possibility to address this problem for me it to change the select statement in the plugin.

It should not only search for changeitems where the field is named "status", but also restrict the search with

fieldtype = "jira", so that custom field with a similar name (like upper case "Status") are not selected.

This can be done in line 106 of the file TransitionsManager.java.

Since you are now working on the code, can you please add this restriction to the final 0.6 release?

I think it's just a small fix that can help other inadvertent jira-admins not getting the null pointer.

Thanks,

Bettina 

 Hello Alexey,

 I have a problem when I add the copy field post function to a workflow.

 The souce and destination fields are both custom fields of type date picker.

 Maybe this type is not yet implemented?

The error log I get is this: 

2007-05-04 13:02:22,914 http-443-Processor23 ERROR [atlassian.jira.workflow.SimpleWorkflowManager] Error occurred while creating issue. This could be due to a plugin being incompatible with this version of JIRA. For more details please consult the logs, and see: http://confluence.atlassian.com/x/3McB
java.lang.ClassCastException: java.lang.String
    at com.atlassian.jira.issue.customfields.impl.DateCFType.getDbValueFromObject(DateCFType.java:30)
    at com.atlassian.jira.issue.customfields.impl.AbstractSingleFieldType.createValue(AbstractSingleFieldType.java:117)
    at com.atlassian.jira.issue.fields.CustomFieldImpl.createValue(CustomFieldImpl.java:574)
    at com.atlassian.jira.issue.fields.CustomFieldImpl.updateValue(CustomFieldImpl.java:330)
    at com.atlassian.jira.issue.fields.CustomFieldImpl.updateValue(CustomFieldImpl.java:312)
    at com.atlassian.jira.workflow.function.issue.GenerateChangeHistoryFunction.execute(GenerateChangeHistoryFunction.java:76)
    at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:869)
    at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1265)
    at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:567)
    at com.atlassian.jira.workflow.SimpleWorkflowManager.doWorkflowAction(SimpleWorkflowManager.java:263)
    at com.atlassian.jira.workflow.WorkflowTransitionUtilImpl.progress(WorkflowTransitionUtilImpl.java:264)
    at com.atlassian.jira.web.action.issue.CommentAssignIssue.doExecute(CommentAssignIssue.java:218)
    at webwork.action.ActionSupport.execute(ActionSupport.java:153)
    at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54)
    at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132)
    at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:209)
    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.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16)
    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:41)
    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.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:49)
    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 com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39)
    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.valves.AccessLogValve.invoke(AccessLogValve.java:541)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
    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:595)

 Cheers

Bettina 

hi 

do we have any special install instructions or we just copy the jar file under jira-install/common/lib, can some one confirm this as i need to work on this.

Thanks

Hi Alexey and others

Please have a look on below issue

Kaamelot

Non functional with JIRA 3.9...

I just have search  something like this but

it isn't work with Enterprise Edition Version 3.9-#233 for me

 I have an error in loading plugin and it is disabled

*Error:*There was a problem loading the descriptor for module 'workflow-condition' in plugin 'JIRA Suite Utilities'. Error retrieving dependency of class: com.atlassian.jira.plugin.workflow.WorkflowUserIsInAnyGroupsConditionPluginFactory. Missing class: com/atlassian/jira/plugin/workflow/WorkflowPluginConditionFactory

Emilia 

So sorry

It was my mystake.

Of course it works, and previous release too

Emilia 

Date Compare Validator compares Date and Time, when it is asked to compare dates only

I have 1 custom field which is of type Date Time and another custom field which is of type Date.

In my work flow transitions i am doing a date compare for the 2 fields and i have set the 'Include time part' flag to No, so that the time element is ignored.

However, while testing i am expierencing a behaviour where date comparator is comparing againt the time.

Steps:

• Set the Date Time field to 12/06/2007 14:00 PM
• Set the Date field to 12/06/2007
• Initiate workflow transition
• Notice that the transition caompares the time element and hence an error is received

How can i rectify it??

Cheers

New version 0.6-EA4 with little bugfix

Download - http://code.google.com/p/jira-suite-utilities/downloads/list
Version history - http://code.google.com/p/jira-suite-utilities/wiki/VersionHistory

Hi all, need some advice..

I have a requirement for the jira user to do a workflow action 'once', and the step have to remain e same. The workflow action leads to a update page. After the updated page is submitted, the action will no longer be available.

My approach was first create a transition, that has the same destination of e current step.
OSWorkflow has no problem with flowing back to the same step.

Next, NULL check using 'ValueFieldCondition' on the value that was to be updated was added.
However I encountered error when submitting the update page.
It seems OSWorkflow ran the condition checks again on submit.

Any advice?

The error stacktrace:
2007-06-26 09:52:14,593 http-8080-Processor14 ERROR [atlassian.jira.workflow.SimpleWorkflowManager] An exception occurred
com.opensymphony.workflow.InvalidActionException: Action 11 is invalid
at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:562)
at com.atlassian.jira.workflow.SimpleWorkflowManager.doWorkflowAction(SimpleWorkflowManager.java:269)
at com.atlassian.jira.workflow.WorkflowTransitionUtilImpl.progress(WorkflowTransitionUtilImpl.java:264)
at com.atlassian.jira.web.action.issue.CommentAssignIssue.doExecute(CommentAssignIssue.java:218)
at webwork.action.ActionSupport.execute(ActionSupport.java:153)
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132)
at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:209)

Hi, can i request the method CommonPluginUtils.getValueFieldConditionFields() line 432 to be removed?

allFields.removeAll(getAllDateFields());

This will allow some form of date checking e.g.
Due Date equal to NULL. Compared like String

Thanks

Hi,
a question to all JIRA Suite users: What are you thinking about to change the aditional issue-tab 'Transistion Summary' to a 'Transistion Histirory'. Our JIRA users really like this illustration of status changes but this view will often misinterpreted in terms of 'the bottom line isn't the last transition'. Of course this information is also in the history tab but not in this nice and much easier to read view - and often hidden between tons of other changes.

I would really appreciate your opinions.

Cheers,

Alexander

Hello,

I find this plugin very useful.  Thank you very much for publishing it.

I was bummed to find that it doesn't play well with Atlassian's "JIRA Toolkit Plugin" custom fields.  Specifically, I wanted to create a "user picker" custom field named "Resolved By" and have a workflow action copy the "Assigned to" value to the "Resolved By" user picker custom field via a workflow transition post function.  This would allow one to search by "Resolved By" using the user picker control - VERY useful for, say, auditing of a new developer's work.

Unfortunately, the latest version of your pluging throws an error if I try to do this.  This only works if I use a text field as the target field.  This is ok, but it's not great, as you have to know the username to search for.

One other addition that would be great is if one could copy the "FixVersion" into another field (even a text field).  the version fields do not appear in the list of available target fields for the "copy field value to anotehr field" workflow post functions.

Just some suggestions to make a great plugin even better.

 - Will

I copied the details for the JIRA Toolkit plugin below. 

JIRA Toolkit Plugin

Description: JIRA Toolkit Plugin: A collection of useful Custom Fields
Vendor: Atlassian Software Systems
Plugin Version: 0.7.20
Jira Version: 3.7

New version 0.6

Download - http://code.google.com/p/jira-suite-utilities/downloads/list
Version history - http://code.google.com/p/jira-suite-utilities/wiki/VersionHistory

Hi All,

I've tested the 0.6 version of this plugin in Jira 3.9.2 and more especially the "Fields Required" workflow validator.

On the Resolve Issue transition, I've set the "Fix version(s)" field mandatory.

When trying to resolve my issue without having set the "Fix version" field, I have on the screen the red tooltip indicating that the "Fix version(s)" field is required (cool!) but I have in Tomcat the following exception, as if the exception was not caught:

2007-07-18 14:11:29,446 WARN [webwork.view.taglib.IteratorTag] Value is null! Returning an empty set.
2007-07-18 14:11:35,274 ERROR [atlassian.jira.workflow.SimpleWorkflowManager] An exception occurred
[InvalidInputException: [Error map: [{fixVersions=Fix Version/s is required.}]] [Error list: [[]]]
    at com.atlassian.jira.plugin.workflow.validator.FieldsRequiredValidator.setError(FieldsRequiredValidator.java:127)
    at com.atlassian.jira.plugin.workflow.validator.FieldsRequiredValidator.validate(FieldsRequiredValidator.java:91)
    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: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:178)
    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:64)
    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:595)  

Then, when I select a fix version, I can close the issue and I have no other traces in the logs.

 Do you have any clue ?

 Cheers,

Cécile 

- Value Field: it allows to execute the transition on the basis of the value of a field.  

 'Value field' is currently a condition. Can you make Value Field as a 'validator'? So that it validates that a field is equal/not equal/greater/less than a given value. That would be very helpful.

Alexey,

     I use JIRA 3.7.4 Enterprise and I am currently using jira-suite-utilities-0.5.4. I think the suite fails in a peculiar condition for Field Required Validator.

Suppose you have a custom field that is associated to 2 of the 5 issue types and you are performing a validation by making it mandatory during 'Resolve'. In the case of an issue type with which the field is not associated it throws the 'field required error in the tomcat log but doesnt say anything on the web page. It also stops the transition. The result is no error is thrown on the web page and transition doesnt happen, annoying the user.

I have made changes to the 0.5.4 code. Should I attach it here or send it to you.

I can send it to you, if you ping me at raghukumar.c <attherate> tavant.com 

Thank you Gustavo and Alexey for the great plugin

-raghu 

Hi All!

I've got a problem with the last version of this plug-in in JIRA 3.10.2 

I'm getting an exception in Transition tab whenever it contains transitions performed by a user that has been deleted from the system:

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- com.opensymphony.user.EntityNotFoundException: No user dda found at com.opensymphony.user.UserManager.getEntity(UserManager.java:302) at com.opensymphony.user.UserManager.getUser(UserManager.java:193) at com.atlassian.core.user.UserUtils.getUser(UserUtils.java:31) at sun.reflect.GeneratedMethodAccessor287.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:267) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:197) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:128) 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.ASTIfStatement.render(ASTIfStatement.java:70) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:172) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) 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.........

 In the Comments tab JIRA handles missing user with no problem.

Can this bug be fixed? 

New version 0.6.1

Download - http://code.google.com/p/jira-suite-utilities/downloads/list
Version history - http://code.google.com/p/jira-suite-utilities/wiki/VersionHistory

Hello,

I use "Value Field" as a Condition on resolve issue (Time Spent >0)
As a result, I cannot Start Progress / Resolve / Close the issue when the time is 0..

I don't see why the condition applies also to start progress and close. It should only prevent to resolve
Thanks,

Jean-Pierre

Hi Everyone,

Is it possible to require comment on the resolve issue screen (with the help of plugin being discussed) - something like on the link below: http://forums.atlassian.com/message.jspa?messageID=257250663
?
(I cannot get the latter compile)

Regards,
Alexey

Hi! 

i want know if this version (0.6.1) is compatible with JIRA 3.11. is?  

I want to use 'Update Custom Issue Field' to update a multi-line field.  However it only allows update of single line of text.

Is it possible for me to amend the plugin so that the input becomes a multi-line text box?

There was a comment posted last year by Reid Sayre that I have not seen addressed anywhere on this forum regarding the addition of "Time Tracking" as an option for "Required Fields".  Is there a chance that this might happen?  It would be very helpful in requiring developers to populate the "Original Estimate" field.

Thanks.

I'm having an issue with notifications, and I suspect that issue may be related to this plugin, since I only see the issue on transitions that include JIRA Suite Utilities (JSU ) post-functions. But before I entered an issue I thought I'd post here and see if someone could tell me if I'm doing something wrong.

 The setup: we have two custom fields of type User: "Code Reviewer" and "Tester". When an issue is Assigned to an engineer, the lead developer also specifies a user in the code reviewer field, and a user in the tester field. Then, when the engineer finishes work on the issue, the engineer executes the "Send to Code Review" transition. This transition puts the issue in our Code Review workflow state, and uses the JSU "Copy Value from Other Field" post function to copy the value from the Code Reviewer field to the Assignee field. The "Send to Test" transition works in a similar way, copying the user from the "Tester" field to the Assignee field.

On my JIRA Pro 3.10 installation, with JSU 0.54, the users would be assigned correctly but the notifications didn't behave as expected. The notification for the Send to Code Review transition would go to the former assignee (the engineer) instead of the Code Reviewer, and there was no notification at all for the Send to Test transition. I tried upgrading to JSU 0.6 last night, and after I did that, the post function apparently stopped working. The workflow transition would execute, but the assignee wouldn't update to the Code Reviewer. After I reverted to JSU 0.54, that started working again.

Something else I noticed - even with JSU 0.54, the change to the assignee didn't show up in the issue's change log. 

So, am I doing it wrong?   Is there something special about the Assignee field such that trying to copy from another user field won't work?

Thanks in advance,

James 

We have a problem with the plugin (both 0.5.4 and 0.6.1), specifically with the Fields Required validator. The list of the available fields does not include Original/Remaining Estimate field. The Time tracking is ON. It's strange that we have the problem on our production Jira 3.6.4 Pro, but it doesn't appear on the test installation of Jira 3.6.4 Enterprise (only 0.6.1 was tested). What could be the reason for this?

Thanks in advance.

Hi,

This sounds like a great and useful plugin ! Thanks !

Before I decide to go for installing it (strict install procs here ) I've got a simple question I cannot read an answer for: does the Workflow Condition "Field value" allow to define conditions on Custom fields?

Thanks

Regards,

Hi,

is it possible to use version 0.6.1 with JIRA 3.11 ?

Regards, Klaus

I have version 0.5.3 of these utilities and found that the Resolution field cannot be cleared by these utilities. Other fields seem fine.

Hi,

one single, simple and stupid question : how do I remove a Validator? (cf. the Validators.jpg attached file) (My workflow in INACTIVE (I can add Conditions for instance)).

Thanks !

Hello!

What does "retroweaved" mean?

What is the difference between standard version and retroweaved version?

Does it relate to the java version I'm using? But then which version is for which java???

... now I see, it is for JVM 1.4!

It's explained in the change history. OK then!

Bettina

Which Custom Field Type can be copied by the post-function to the JIRA built-in Assignee field?

I've tried User Picker and Select List types without any sucess.

Can anyone confirm this plugin 0.6.1 is compatible with JIRA 3.12? The compatibility chart at the top hasn't been updated to indicate this.

Copy Value From Other Field doesnt work for me.

I am trying to copy the value of a custom field (simple single line text input) to Description field.  The transition runs OK but the value is not copied.

JIRA 3.11 + Suite Utilities 0.6.1

We are on JIRA 3.8 and plugin ver 6. We've been using this for a while without noticing a problem. Over the weekend I modified a workflow and added a second transition out of a status. The new transition has similar, but not exact fields required as the original transaction. Now neither transition is requiring the correct fields. It is requiring some, but not all. Has anyone seen this before?

Has any one else had the problem where Update Issue Custom Field does not show up in Change History?

We are using this post function to update a Text Field, and it works fine, except that we would like this change to show up in Change History as it would if the change had been made manually via an Edit operation.

If this is by design, does anybody know how we could enable this update to show up in Change History? 

Thanks!

We're running java-suite-utilities-0.6.1 with JIRA 3.12.1.

New version - 0.6.2

Only one little bugfix + integration with google maps.

I'm also having an issue with the "Copy value from other field".  The error message being displayed is "Unable to copy value from Reporter to Verifier"

I'm trying to copy the value from the Reporter to a custom field (user picker) named Verifier.  I'm using a custom workflow with a bunch of different transition screens. 

I see from the mesages that people have had issues with this feature in the past and that there are issues still open for this on the google code page.  I was wondering if you had an idea of when this would be fixed

 I'm running Jira 1.10 with JIRA Suite Utilities 0.6.1

Hi,   I forgot to install the plugin after upgrading to 3.12.2.  I got this error

Type: class
Class: com.atlassian.jira.plugin.workflow.condition.UserIsInAnyGroupsCondition
Arguments:
hidGroupsList = HD-tier3@@jira-developers@@PIDI-BS@@PIDI-Dev Managers@@PIDI-Developers@@PIDI-QA@@HD-tier2@@jira-administrators@@

I then went back and installed it, I can now add new security, but the old ones, existing security is still erroring out.  We are trying to go live today, so any help would be greatly appreciated.

A lot of bugfix and new version is ready - 0.6.3

I am using the Clear Field Value plugin in a workflow inJira Enterprise 3.12.2 and it's not clearing the assignee field, which is the one I have specified in the workflow for it to clear. It's not putting any errors in the log, it's just not doing anything.

ETA: I upgraded to 0.6.3 and the problem still exists.  In fact, I had to delete and recreate all my post functions from 0.6.1 because, while the plugin showed up as correctly installed and enabled under Plugins, the post function in the workflow showed up like a generic missing post function does -- just the name of the class and the fields it gets passed, instead of the pretty way with edit/delete/moveup/movedown links and the template from clearfieldvalue-view.vm. However, even after recreating them, the Assignee field is not purged. 

Hi. We were trying to do the following, set the assignee using the CopyValueFromOtherFieldPostFunction post-function. It wasn't working, so I downloaded the code and fired it up in the debugger. After a few minutes I realised that the package names have changed - in the jar "jira-suite-utilities-0.6.jar", the class and package is com/atlassian/jira/plugin/workflow/function/CopyValueFromOtherFieldPostFunction. When downloading source, it is com.googlecode.jsu.workflow.function. This actually works when compiling from source.

I am confused, which is the correct and maintained version I should use? If it's the google code one, how would one "migrate" to it, given that if I put that in as well as the previous one all the workflow functions will be shown twice, and if I just delete the previous one, any workflows that use those functions will stop working?

cheers, jamie

Hi,

 I am in face of a blocked issue: unable to create an issue and this error is returned "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@17eca50: root cause: Issue cannot be null. "

In first I met this issue with Jira 3.11-#288 & Jira.utilities plugin version 0.6

I upgared the plugin to version 0.6.2: it was working fine but today we re-meet this issue.

In workflow, there are 2 validator functions:

Only users with Create Issues permission can execute this transition.
— AND
Fields required for this transition: Assignee
 
  
Any idea about that?
 
Thanks,

Hi,

We are using the 'Copy Value From Other Field Post Function" (in jira-suite-utilities-0.6.3) and am getting the error "Error creating issue: com.atlassian.jira.workflow.WorkflowException: com.opensymphony.workflow.WorkflowException: Unable to copy value from Priority to Branch Priority."

2008-03-18 14:10:23,625 http-8080-Processor24 ERROR [com.googlecode.jsu] Unable to copy value from Priority to Branch Priority
java.lang.RuntimeException: class com.atlassian.jira.issue.customfields.impl.SelectCFType passed an invalid value of type: class com.atlassian.jira.issue.priority.PriorityImpl
    at com.atlassian.jira.issue.customfields.impl.AbstractCustomFieldType.assertObjectImplementsType(AbstractCustomFieldType.java:107)
    at com.atlassian.jira.issue.customfields.impl.SelectCFType.getStringFromSingularObject(SelectCFType.java:77)
    at com.atlassian.jira.issue.customfields.impl.StringCFType.getDbValueFromObject(StringCFType.java:20)
    at com.atlassian.jira.issue.customfields.impl.AbstractSingleFieldType.createValue(AbstractSingleFieldType.java:117)
    at com.atlassian.jira.issue.fields.CustomFieldImpl.createValue(CustomFieldImpl.java:574)
    at com.atlassian.jira.issue.fields.CustomFieldImpl.updateValue(CustomFieldImpl.java:330)
    at com.atlassian.jira.issue.fields.CustomFieldImpl.updateValue(CustomFieldImpl.java:312)
    at com.googlecode.jsu.util.WorkflowUtils.setFieldValue(WorkflowUtils.java:309)
    at com.googlecode.jsu.util.WorkflowUtils.setFieldValue(WorkflowUtils.java:495)
    at com.googlecode.jsu.workflow.function.CopyValueFromOtherFieldPostFunction.execute(CopyValueFromOtherFieldPostFunction.java:53)
    at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:869)
    at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1265)
    at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:618)
    at com.atlassian.jira.workflow.SimpleWorkflowManager.createIssue(SimpleWorkflowManager.java:189)
    at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:365)
    at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:313)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:71)
    at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
    at $Proxy9.createIssue(Unknown Source)
    at com.atlassian.jira.web.action.issue.CreateIssueDetails.createIssue(CreateIssueDetails.java:141)
    at com.atlassian.jira.web.action.issue.CreateIssueDetails.doExecute(CreateIssueDetails.java:110)
    at webwork.action.ActionSupport.execute(ActionSupport.java:153)
    at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54)
    at webwork.di