On my backlog, I used to see different EPICs in different colors (easy way to group user stories). I don't have anymore this possibility.
Thanks.
Sorry about that, I introduced this error in 1.3.3, fixed it for 1.3.4 which will be released later today. See https://studio.plugins.atlassian.com/browse/JSUTIL-155
Thank goodness it's something that can be fixed, I was pouring over everything. I eagerly await the fix.
Can you explain why it only triggered for me with Fix Versions as the requirement but not other requirements?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bryan I just upgraded to 1.3.4 and I'm still facing this issue. Could you update this thread after you've upgraded the plugin also?
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The new 1.3.4 version did correct the problem for me. When I go back in and re-enable the Fix Versions requirement it no longer gives me that error.
If you're still having a problem with the validators, perhaps go into your workflow, remove them. Publish, then go back in and re-add them again and see if that fixes it up for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm weird. It worked when I removed the validator (Required fields: Affects Version/s ) for the Create transition. But after I added it again it fails.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can confirm if I add "Affects Versions" to my list of required feilds it gives me the error again.
The problem I was having was adding Fix Versions and the 1.3.4 update fixed that. So I think we may need another update to fix the "Affects Versions" and anything similiar to that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for verifying this. I am unable to upgrade outside my sandbox until this gets resolved. Stephan please let me know if there's anything I can do to provide the necessary feedback for this to get resolved. Thanks for the effort.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
While it may be already in the works, I opened a bug report for this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for verifying this. I am unable to upgrade outside my sandbox until this gets resolved. Stephan please let me know if there's anything I can do to provide the necessary feedback for this to get resolved. Thanks for the effort.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.