Whenever I ask the testers to Log issues from their handsets using JIRA JMC(mobile connect), there is a unique UUID associated with the issue which helps in replying back to the device.
Whenever I edit the issue in JIRA project through web portal, say categorize it as per priority, I loose the UUID (since UUID is not shown in web portal/ website because of security and other issues, i read it is a hidden field) and hence can't be manually entered.
So my question is how should I edit such issues in the project from web portal so that the link is not broken?
I see that once i edit the issue, UUID is deleted by itself and we can't edit since ot is hidden, and the comments are not posted back to the device/tester handset. Till I don't edit issues, comments are posted perfectly.
Thanks for the suggestion Jason. I tried the approach but reposting using API doesn't help as still the links for previous edit are deleted. Plus it makes even more confusion in case of Android devices for end testers. It's like every time you edit, you are creating a duplicate.
I guess the best way was to make a single duplicate for tracking/edit as a parallel and let the original conversation be as is.
This sounds like a catch 22 situation. If the field needs to remain as hidden, then the only suggestion I can think of would be to try using the RESP API to repost again to get the UUID back. Not sure if that will work but wanted to mention it as a possible workaround.
Hope this helps!
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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