Issue 173 in jira-suite-utilities: Support for Jira 4.3
jira-suite...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 173 by leindirk: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Please provide compatibility to JIRA 4.3 and state this on in the Plugin
Exchange https://plugins.atlassian.com/plugin/details/5048
Thanks,
Dirk
jira-suite...@googlecode.com
Comment #1 on issue 173 by polderva...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Do you know for sure that it doesn't work with 4.3? We're about to upgrade
4.1.2 to 4.3 in the next day or two and were *assuming* that it would work.
jira-suite...@googlecode.com
Comment #2 on issue 173 by leindirk: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
If it works in 4.3? I have no clue, but our IT would refuse to install it
if has the "X" for 4.3 on the compatibility table.
jira-suite...@googlecode.com
Comment #3 on issue 173 by ale...@abashev.ru: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Right now it doesn't work in 4.3. And I'm fixing it.
jira-suite...@googlecode.com
Comment #4 on issue 173 by polderva...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Hi.
Can you give me any indication of what doesn't work and when you think it
will be ready? Like I said we were about to start the upgrade tomorrow
before we go live with our first production use of jira. Are we looking at
days our weeks our months away? No pressure. :)
jira-suite...@googlecode.com
Comment #5 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
I think I need one week or so.
jira-suite...@googlecode.com
Comment #6 on issue 173 by polderva...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Thanks! Is there a specific bug, or does it all not work? If its a bug in
something we don't use, then we could start our 4.3 upgrade, and upgrade
the jira-suite-utilities after that.
Sorry to keep asking for details. Just trying to figure out if we can
still proceed with the 4.3 upgrade and continue our pilot test.
And thanks for the great plug-in. It is definitely helping us get off our
old bug tracking system and onto JIRA.
jira-suite...@googlecode.com
Comment #7 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Version 4.3 have lost i18n bean and I need to fix it. Also there are a lot
of deprecated apis and fixes for DI.
jira-suite...@googlecode.com
Comment #8 on issue 173 by polderva...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Hi Alexy, We are continuing with our upgrade to 4.3 for our JIRA pilot.
The installer went ahead and installed Jira Suite Utilities. For the
functionality that we are using, it appears that only the Field Validator
is causing problems. The Update Issue Custom Field post-function is
working as expected.
Until your 4.3 compatible update, I pulled out the Field Validators to
continue with our JIRA testing. Hopefully you are making progress on a 4.3
update. :)
Thanks,
Robert
jira-suite...@googlecode.com
Comment #9 on issue 173 by Jens.Deh...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
I've also updated to Jira 4.3 and found this things out:
-the "clear field" entrys in the workflow where still there after
migrating, but one can not create a new post-function like that. I didn't
try yet if it's working
-the "fiels requiered-validator" was not ported to jira 4.3 and is
definitly not working any more in 4.3
This were all fields used by us...Thanks for the plugin and for fixing it
to work on 4.3
jira-suite...@googlecode.com
Comment #10 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Guys, I'm not able to do full coverage testing right now. So please take
version from attachment and try it in your environment. As fast you will do
tests as fast I will release new version.
Thank you.
Attachments:
jira-suite-utilities-0.8.1-SNAPSHOT.jar 114 KB
jira-suite...@googlecode.com
Comment #11 on issue 173 by jus.ha...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
I'm getting errors when clearing custom fields using that snapshot. e.g.
Unable to update custom field 'customfield_10030 - Requirement Review
Accepted'
jira-suite...@googlecode.com
Comment #12 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Thank you for the report. New version was attached.
Attachments:
jira-suite-utilities-0.8.1-SNAPSHOT.jar 114 KB
jira-suite...@googlecode.com
Comment #13 on issue 173 by jus.ha...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Looks like that's fixed that problem thanks!
jira-suite...@googlecode.com
Comment #14 on issue 173 by polderva...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Hi. I have downloaded the -0.8.1-SNAPSHOT.jar and will test this as soon
as it is installed. Unfortunately, the person doing the installs has left
for a long weekend. We'll get it installed as soon as he returns.
Thanks for the quick work.
Robert
jira-suite...@googlecode.com
Comment #15 on issue 173 by chriscow...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
-0.8.1-SNAPSHOT.jar has appears to be working for me.
jira-suite...@googlecode.com
Comment #16 on issue 173 by pen...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
I can verify that this fixes Issue Creation when you have workflows enabled
on the custom fields.
jira-suite...@googlecode.com
Comment #17 on issue 173 by nes...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Hi,
I get error when clear issue field using that snapshot's jar.
Could not load FunctionProvider class
Thanks.
jira-suite...@googlecode.com
Comment #18 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Try it with second snapshot. This bug should be fixed there.
jira-suite...@googlecode.com
Comment #19 on issue 173 by nes...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
actually i tried both of them. Doesnt work.
I tried to clear "due date" field. But i get error.
jira-suite...@googlecode.com
Comment #20 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
That is problem with your installation. Did you clean all caches and temp
files. Can you remove all other plugins and test it on clean installation?
That can help to find 'conflicting' plugin.
jira-suite...@googlecode.com
Comment #21 on issue 173 by nes...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
OK, It is working.
Thank you for your help.
Regards.
jira-suite...@googlecode.com
Comment #22 on issue 173 by polderva...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
We have installed the latest version and the field validation is now
working! We are only using the Field Validation and Update Custom Field
post-function. Both are working as expected.
Thanks,
Robert
jira-suite...@googlecode.com
Comment #23 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Great, there will be no more bug reports I will release at next Monday
jira-suite...@googlecode.com
Comment #24 on issue 173 by vic...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Upgraded JIRA from 4.1.2 to 4.3, and a lot of transitions broke since I
have Post-Functions using this plugin in a lot of the steps.
I will be installing this new version (second attachment) in about 15
minutes... having fingers crossed that all will work. I will keep you
posted. Thanks Alexey, this is a wonderful plugin!
jira-suite...@googlecode.com
Comment #25 on issue 173 by vic...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
the Post-Function options didn't show up. Darn! Any clue?
jira-suite...@googlecode.com
Comment #26 on issue 173 by vic...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Neither are the Condition options are showing up
jira-suite...@googlecode.com
Comment #27 on issue 173 by nes...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Do you enable plugin ? administration-->system-->plugin
when i installed, it was disabled.
jira-suite...@googlecode.com
Comment #28 on issue 173 by vic...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Yes, the plugin is enabled
jira-suite...@googlecode.com
Comment #29 on issue 173 by vic...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
IT WORKED!! Based on Alexey's response, I deleted .osgi-plugins
and .bundled-plugins from the Plugins folder. Once I copied the plugin
file and restarted JIRA, those two folder were I guess rebuilt, fresh, and
my issues were resolved. Thanks Alexey!
jira-suite...@googlecode.com
Comment #30 on issue 173 by javier.o...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
The attached file works great on JIRA 4.3.
jira-suite...@googlecode.com
Comment #31 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Guys, first of all I want to say thank you for everybody for the testing.
Your help was really appreciated and it help me to move forward to the next
JSU release.
But yesterday, right before I was ready to do release, I've got very
strange message from Atlassian. And till I'll get additional explanations
I'm not sure about JSU future. So please do repository backup from github
and wait a little while. I hope everything will become clear and we don't
have to worry.
Thank you.
jira-suite...@googlecode.com
Comment #32 on issue 173 by cyril.e...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Hi - Any update on your comment on Apr 5?
When do you expect clarification by?
jira-suite...@googlecode.com
Comment #33 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Not yet.
jira-suite...@googlecode.com
Comment #34 on issue 173 by jijo.jo...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
We have installed the plug-in on our test JIRA setup and is working fine,
downloaded from the above post.
Could you please advice, can I take that to production environment? We have
been waiting for this quite sometime..
Thank you..
jira-suite...@googlecode.com
Comment #35 on issue 173 by al.meckl...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
I am close to getting jira-suite-utilities-0.8.1-SNAPSHOT.jar (the one from
Comment 12) to work. However, I’m having the same problem “nes” has in
Comment 19: I get “Could not load FunctionProvider class”.
When installing JSU, I
1) stopped Jira
2) deleted HOME\plugins\ .bundled-plugins and .osgi-plugins (as suggested
in Comment 29)
3) copied jira-suite-utilities-0.8.1-SNAPSHOT.jar to
\atlassian-jira\WEB-INF\lib
4) restarted Jira
5) from admin > plugins I had to enable JSU (it initially was disabled)
6) the primary function from JSU that we use is “Copy Value from other
Field”; it shows up as an available Post Function, so I thought we were set.
However, it doesn’t work, giving the error I mention above. I’ve attached
what appears to be a log file being dumped to a DOS window via Tomcat. It
seems to indicate that the “copyValueFromOtherField-function” is not
enabled (even though it appears to be in Admin > Plugin.
So, nes, are you there? In Comment 21, you say you got it working. What
did you do?
Alexy, thoughts? You mention in Comment 20 cleaning “all caches and temp
files”, can you send a list of exactly which/where these files are?
BTW, I’ve been in contact with Atlassian ever since I read Alexy’s rather
ominous-sounding Comment 31. As far as I can tell, Atlassian is talking
with him re making JSU available on the Plugin Repository (and installable
via the Universal Plugin Manager: Admin > Plugins). Which would be great,
but here, right now, we’re in critical need of at least an interim version
to allow us to get Jira 4.3 into production
Attachments:
JSU error.txt 14.8 KB
jira-suite...@googlecode.com
Comment #36 on issue 173 by al.meckl...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Ah ha! Issue # 176 suggested that maybe I should try installing the
Snapshot in \Home\plugins\installed-plugins instead of where I did. I did
all of the above in Comment 35, but installed it to installed-plugins.
Seems to work now, at least the “Copy Value from Other Field” Post
Function, which is what we need to process with our upgrade.
Looking forward to a version that’ll be available on the Atlassian Plugin
Exchange.
jira-suite...@googlecode.com
Comment #37 on issue 173 by ccu...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Any update about the future of this excellent plugin?
We've just upgraded to Jira4.3 ... :(
jira-suite...@googlecode.com
Comment #38 on issue 173 by javier.o...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Read through. There's a snapshot that's working for me on 4.3
jira-suite...@googlecode.com
Comment #39 on issue 173 by umvel...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
"Fields Required" at jira-suite-utilities-0.8.1-SNAPSHOT.jar not working
for me: "Could not load validator class".
jira-suite...@googlecode.com
Comment #40 on issue 173 by umvel...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
"Clear Field Value" at jira-suite-utilities-0.8.1-SNAPSHOT.jar not working
for me: "Could not load FunctionProvider class"
jira-suite...@googlecode.com
Comment #41 on issue 173 by david.k...@cdnorthamerica.com: Support for Jira
4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
CD-adapco needs this plug-in for 4.3 as well. We want to upgrade to 4.32.
We use the user in groups (easy to work around); value field (not so easy
to work around); and Fields Required validator.
Fields required is so basic. Isn't there another plug-in or standard
feature in Jira to handle this? I guess you would have to make the field
required at the field level instead of workflow? But then it would always
be required, regardless of the transition you were executing, which is not
the same thing.
Thanks,
David
jira-suite...@googlecode.com
Comment #42 on issue 173 by krad1...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Is the jira-suite-utilities-0.8.1-SNAPSHOT.jar still available? If so, can
someone post the link?
jira-suite...@googlecode.com
Comment #43 on issue 173 by brady.ki...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Excuse my ignorance, but I do not see the
jira-suite-utilities-0.8.1-SNAPSHOT.jar file attached in the thread. I
upgraded to JIRA 4.3 and began to have problems with transitions in my
workflows.
Thanks!
jira-suite...@googlecode.com
Comment #44 on issue 173 by abas...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
If you did not see this before -
https://docs.google.com/document/pub?id=1rQHVvveok-pBLYEkcvDykiRyljyen5mvy0YUmb31FsU
Will be no JSU or any upgrades for 4.3
jira-suite...@googlecode.com
Comment #45 on issue 173 by krad1...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
This is really too bad. JIRA is really crippled without the features in
this plugin. I guess the only option is to remain on 4.2 until someone
else takes over the code or duplicates the features in another plugin.
jira-suite...@googlecode.com
Comment #46 on issue 173 by brady.ki...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
"Will be no JSU or any upgrades for 4.3"
Fair enough. I would probably update the front page to say that. It's not
clear from the document.
jira-suite...@googlecode.com
Comment #47 on issue 173 by jus.ha...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Hmm I'm running the snapshot on 4.3 and it works fine. But if there's going
to be no official version, and no future versions compatible with future
versions of JIRA, then I'm worried. Can't afford to rely on the
functionality for our company's install only to lose that later on if we
want to upgrade JIRA. Unfortunately we really needed it for some of the
workflows we wanted to do. Going to have to re-evaluate...
jira-suite...@googlecode.com
Comment #48 on issue 173 by polderva...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
Hi Alexey,
I wish you the best of luck working this out with Atlassian. Thank you for
taking over the maintenance of JSU and providing updates. This really is
critical functionality that I would have hoped would be part of the core
JIRA product.
Robert
jira-suite...@googlecode.com
Comment #49 on issue 173 by perangel...@gmail.com: Support for Jira 4.3
http://code.google.com/p/jira-suite-utilities/issues/detail?id=173
We just upgraded JIRA and sorely will miss your plugin. It is a really
essential plugin for us and hopefully we can figure a way to live without
it. I hope things will work out between you and Atlassian because your
plugin is essential to our workflow.
I hope there will be some sort of compromise.