Listeners don't have any access to the UI - they're background things that are usually triggered by user activity, but don't have to be.
Also, they happen *after* user activity. So you would never be telling a user "you are not allowed", you would be telling them "it failed".
Still, allowing add-ons (sorry, apps) to send messages to users (in the form of the message box Jira displays in the top right corner of any page) would be super useful. This could be done through a REST API.
I have raised https://ecosystem.atlassian.net/browse/ACJIRA-1362 for that.
Ok, thank you.
I thought of a new custom field especially for a feedback message that can be updated on the server side as a workaround but that is not a pretty solution for my case.
It would be nice to be able to throw a CustomListenerException("my text") which the standard UI handles automatically as a message like it does on workflow validatiors.
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
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