You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Something seems to have gone very wrong today.
Also, last week, the emails changed behaviour from sending me mail when there was a new topic and on anything I was watching to just sending me mail on all posts on everything (replies and comments on questions I was not watching)
Thanks for the detailed report Nic. Unfortunately there are a few things going on:
Thanks for your patience as we get these sorted out.
Thanks for the update Tyler, it sprung back into life on three points at about 14:30 BST. I was still finding the spam trap a little over-enthusiastic about double quotes for a couple of hours afterwards, but that's gone back now.
But the emails seemed to have stopped again. I'll go update the issue instead of rambling here!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The latency issues have appeared again unfortunately. We will post updates once it has been resolved.
Thanks for sending us your feedback :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't expect this sample to be a lot of help, but yes, the double-quote = spam problem surfaced again (not while there were latency issues as far as I could tell). I snapshotted one that was a great example - with quotes, it was rejected three times. Without them around "events", it sailed through.
-----
That is broadly correct. A listener picks up "events", and the events in Jira (which are triggered by activity of varying sorts) contain a pile of information about what triggered it. They're independent of each other, so any given execution of a listener is based entirely on the data in its own event.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you.. I'm going to look at the logs for that specific issue. There was another minor latency issue that happened again today at Oct 11, 18:58 UTC and was resolved at Oct 11, 21:03 UTC. Regardless, will look into your issue ASAP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is where I miss the "upvote comment" function ;-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
... and emojis by simple text, despite only knowing about four...
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.