The plugin's compatibility matrix isn't very clear on the subject. It appears it should be compatible, but I am receiving an error for any "Edit" screen containg a Velocity processed Message Custom Field (for edit) field. There is a Critical Bug filed against the project from August 8th 2012, however, Atlassian hasn't responded.
Has anyone else encountered this? If so, how did you resolve the problem?
Error (I have the entire error is anyone wants to see it):
com.atlassian.jira.util.dbc.Assertions$NullArgumentException: one should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:28
The short answer is nearly :-)
The Velocity custom fiields don't work because of a bug I've just raised - see https://jira.atlassian.com/browse/JRA-29836
I'm trying to see if I can make a workaround somehow that doesn't rely on a core JIRA fix...
As are we. Atlassian said they are unlikely to work on it as it's a version behind.
The issue was first raised 8/8/12: https://studio.plugins.atlassian.com/browse/JTOOL-157
Hopefully we'll find a solution soon. We are rather excited about some of the performance enhancements in 5.1.x.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs