Why aren't Tempo accounts working in existing queries as of 6/9/17?

As of this morning, 6/9/17, all existing queries our users had that involved Tempo Accounts no longer work.  Prior to today, accounts were referenced by a system-generated number in the Advanced queries.  You can see this by toggling to "Advanced" and viewing the query string.  As of today, the IDs don't work and the account name must be the actual full name of the account in quotes.  Additionally, the  two dimensional filter statistics used to include account in the XAxis and YAxis options, but as of today, account is no longer an option for X or Y.

What changed and how can we get our queries working again without having to recreate them all?

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Featured Groups

Want to know how Atlassians monitor their enterprise deployments?

At Atlassian, we believe in our own products – that's why we use them, even at the enterprise level. Doing so gives us first-hand experience of how they perform at scale; to do this, we monitor each ...

135 views 5 9
View post

Atlassian User Groups

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!

Find my local user group

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

Groups near you