Jira account deactivation emails

[Gijs]

Because of other commitments I have been using my Jira (Cloud Free) instance less frequently recently. On 11-03 received an email "[Action Required] Your Jira subscription will be deactivated due to inactivity soon" stating that, when not using the app, it will be deactivated on 18-03. So I logged in, updated some tasks and even created some other. Doing so, I kind of assumed the 120 day inactivity period would be reset. But today, 15-04, I received yet again an email "[Action Required] Jump back in to Jira to keep your subscription" stating that, when not using the app, it will be deactivated on 29-04. So I logged in again and updated a task but this seems a bit odd. Any ideas if this is normal procedure and/or if the 120 day inactivity period has been changed (/shortened)?

[Mirek]

Welcome @Gijs 

Most likely, nothing changed in the 120-day rule. What’s happening is that Atlassian either didn’t reliably register your login as “Jira activity” at the time the inactivity system checked, or the warning emails were already queued and continued to be sent even after you logged in. A less likely but still possible cause is that you’re using a different Jira site than the one referenced in the email. Is there any or you are sure that it is the only one that you are using? Overall, this is probably a mix of delayed activity tracking and independent email scheduling rather than an actual change in policy.

[Gijs]

Thank you @Mirek for your elaborate reply. I did actually consider (and check) the latter option. I used to have another site, registered with the same email address, but that site has been closed (and, assumingly, removed) for years. The emails I now received both refer to the same, and current site. Let's see if the tasks I edited and created today are properly registered as activity this time, or if I get another email in a month from now :) Interested to see also if other users are possibly experiencing the same issue. What made me think about a possible policy change is that the dates mentioned in the emails are not the same, and essentially have shifted by exactly a month.

[aratogl]

We are experiencing a very similar issue, but in our case Jira was actually deactivated despite confirmed activity.

Our team had vacations during July and August, so naturally there was less active work on Jira issues during that period. However, team members were still accessing and viewing Jira.

I find the apparent shortening of the inactivity period concerning. Development teams should be able to go on vacation or temporarily pause active work on a project without having to remember to periodically perform actions in Jira simply to prevent their Jira site from being deactivated and their project data from eventually being deleted.

More importantly, after receiving Atlassian's inactivity warning on August 24, we resumed active work. On September 1, one of our developers updated an issue and changed its status. Jira itself sent us an email notification confirming this activity.

Nevertheless, our Jira site was subsequently deactivated for "inactivity."

This suggests two problems: the inactivity threshold appears to have become significantly shorter than the previously discussed 120 days, and, more importantly, the deactivation mechanism appears to ignore actual user activity even after an inactivity warning has been issued.

We have opened Atlassian support ticket CA-4227502 and provided Jira's own September 1 email notification as evidence.

This looks like a bug in Atlassian's inactivity detection/deactivation mechanism. I would be interested to know whether other Free Jira users are experiencing the same behavior