As far as I know, no. Not short of examining the current stack which you don't want to do. The idea smells a bit fishy anyway, sounds like you will be too tightly coupled.
I would focus on speeding up the scripted field, or using a read-only custom field that is updated through a listener.
The scripted field calls a web service and Jira is not aware of external events that might change outcome. Rendering will be made role/group and status dependent bringing down load. And we'll see if web service can be optimized.
Thanks for the quick reply!
Yeah, tricky one. Maybe a custom field that has a template that uses js to lazily get the value from the web service. Depends if you want to index the returned value or not... also you could do caching on the web service side, but there will still be a lot of requests if you do a full reindex for instance.
Thank you for valid input. I do not index the returned value as I have the basic information ("commit id's") in another Jira field, the web service returns valuable details in html from our non-Atlassian-supported RCS that some users needs for processing while issues are in certain states. I will plan a load test to see how serious the problems is, then we will act from there
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