JIRA Cloud - Filter Subscription Fields Defaulted

[Jonathan Zschau]

We're running on a JIRA Cloud instance and just noticed that a filter subscription that has been running fine for months has just switched to displaying the default fields instead of the filter-specific fields we defined when creating the filter & filter subscription. 

Has there been an update that introduced a bug or has anyone else seen this happen to their filter subscriptions?

Thanks in advance. 

[Jonathan Zschau · Accepted solution]

Fix rolling out today. Our reports/filters are now functioning properly again.

[John Funk]

Great! Thanks for the update!

[Jonathan Zschau]

Hi Everyone:

The last update I've received from JIRA support was this AM indicating that a fix was in the works, but might not get deployed today (USA Eastern Time Zone) due to the responsible team being located in Sydney. Hopefully this is the case and we'll see a fix in the next day or so. 

[John Funk]

Hi Jonathan,

It is very easy for filters to get changed with realizing it. I would just update the filter to be sure it is using the right columns you want. 

[Jonathan Zschau]

Thanks for the quick response. That's what I originally thought so I modified the filter, saved, reverted and re-saved it as sometimes I've noticed the same. Re-ran the subscription and it's still showing ALL of the default fields, not the fields specific to the filter. Looking at the filter itself and it shows the correct filter-specific columns, but when the subscription runs it comes with all default fields in the email. 

[Jonathan Zschau]

Troubleshooting this a bit more. Created a new filter and tried adding/removing/saving/re-saving filter columns/ changing my default columns and the subscription email report is behaving just as if the Filter specific fields do not exist. 

This just started today, so I'm thinking this could be related to an update that might have gone through with Cloud. 

[John Funk]

Sounds like something weird is definitely going on. I would go ahead and open a support ticket with Atlassian.

https://support.atlassian.com/contact/#/

[Jonathan Zschau]

Thank you, submitted. 

[John Funk]

Please come back here and update the thread once you get it all worked out. Thanks!

[Jonathan Zschau]

Just a small update. They looked into it today and informed me it had always behaved this way and that filter subscriptions always use the user's default columns, not the filter-specific ones. That's just not correct as I have over a year's worth of custom filter subscriptions in my inbox from a variety of weekly and daily subscriptions, each with their own filter-specific columns.

This change definitely happened sometime between June 2, 2020 and June 3, 2020.

Before June 3, 2020 every filter subscription email contained whatever columns were set for the filter subscribed too. 

On/After June 3, 2020 every filter subscription will now only email a report with whatever columns the receiving user has set as their default columns.

[Brian DaRosa]

Agreed I’m having the same issue. This is definitely some update or regression issue and it needs to be corrected. Do you have an update on the fix?

[John Funk]

Just found out that this is a known bug that has recently appeared. You can follow the status and add that it affects your team using this link:

https://jira.atlassian.com/browse/JRACLOUD-74554

You should both do that.  :-)

[Trudy Claspill]

Thank you all for your persistence on this. I also noticed this problem, starting today, and found your post.