Bitbucket Issues deprecated with Atlascode v3.6.0

[marcomura]

Hello everyone,

with the new v3.6.0 we are going to deprecate the Bitbucket Issues functionality.

This decision was driven by several factors, including:

• Atlassian officially deprecated and it's phasing out Bitbucket Issues from Bitbucket, in favor or Jira Issues
• Usage of Bitbucket Issues from the Atlascode extension is negligible, in the order of a single digit per day
• We'd like to focus on things that matter to you 😄

Hopefully, this will not disrupt the workflow of any of you.
In case you really need to work with Bitbucket Issues, you can manually install the v3.4.25 which is the last version supporting them.

Please, let us know if you have any comment or feedback about this change.

Thanks!
-- Marco

[marcomura]

One extra note about the new v3.6.0:

We are restoring the full functionality for the "Filters and Custom JQL" configuration:

Since v3.4.20, it was ignoring all the JQL entries that were automatically created during authentication, since they were not really "custom".

Since v3.6.0, there will be no more JQL auto-created at authentication, leaving only custom entries in the Filters and Custom JQL configuration.

Consequently, since v3.6.0, this will have the side effect that old auto-created JQL entries will now be considered custom JQL entries, and show up in the Custom JQL Filters panel.

You can simply go to the Atlascode Settings, Jira, Filters and Custom JQL, and remove the unnecessary ones.

Thanks!
-- Marco