You may be aware that end-of-life is coming up for self-hosted Jira, and Atlassian is encouraging customers to move to their cloud.
So we plan to migrate our Jira projects in the first half of June, and that may have an impact on you.
Because of licensing limitations, we must now limit our Jira users to just the people who work for Sonar. This means community members will no longer be able to watch / vote / comment on issues in our Jira projects.
That doesn’t mean we don’t still want your input! We totally do!
So what should you do instead? For comments on existing Jira tickets, please open a thread here in the community (or contribute to the one someone else already opened). Ideally, the thread title will start with the ticket number to make the connection easy.
And of course for new features, please contribute to our ProductBoards:
You will still be able to view individual Jira tickets our public projects – but you will no longer be able to vote, watch (get e-mail notifications when there are updates), or comment.
We would have loved a way to continue to allow voting/watching of public tickets (we still think this Community is the best place to have discussions), but there wasn’t anything we could do that didn’t require splitting Jira instances or licensing thousands of users.
should it still be possible to log into Sonarsource Jira with exisiting credentials
or should i sign up again ?
I tried yesterday but could not log in, only the request to enter a security question came up.
We are working on a solution. We’ve made sure access to existing release notes are available (by redirecting to our old Jira server). In the coming weeks, we’ll figure out our long-term strategy. We agree it’s important to have access to full release notes.