Bulk problems

[Aleksei Borzenkov]

Hi guys, I'm having a problem with the new bulk system, similar to the one described in these official tickets: https://jira.atlassian.com/browse/JRACLOUD-96714 and https://jira.atlassian.com/browse/JRACLOUD-98090. I commented the issue as recurring, but it doesn't look like it will be re-opened. I can't create a ticket for the cloud-related project, it doesn't appear in the options. Is there any way to contact Atlassian so they can investigate?

[Marc -Devoteam- · Accepted solution]

Hi @Aleksei Borzenkov 

Contact Atlassian Support an raise an issue based on your findings.

[Aleksei Borzenkov]

Many thanks, will do it

[Gabriela · Accepted solution]

The reason you can't create a ticket against the cloud project on jira.atlassian.com is that it isn't a support channel. That site is Atlassian's public bug tracker, where you can watch and comment on JRACLOUD bugs like the two you found, but not open your own support request. Commenting "this is recurring" adds a vote/impact signal, it doesn't reopen a closed bug by itself.

For an actual support request on Cloud, the route is https://support.atlassian.com/contact. One catch that trips people up: if your site is on the Free plan, you only get Community support, so the raise-a-request option won't show for you there. Standard and up get direct ticket support. So if the contact form won't let you open a case, that's usually the plan, not a bug.

Which plan is your site on? That decides whether you can raise a case directly or whether the path is community + voting/watching the two JRACLOUD tickets so you get notified when they move.

[Arkadiusz Wroblewski · Accepted solution]

Hello @Aleksei Borzenkov 

Since your site is marked as Jira Cloud Premium, you should have access to direct Atlassian Support.

From my own experience, the new bulk-edit functionality can sometimes behave unexpectedly or appear buggy.

As @Marc -Devoteam- mentioned, the best next step is to contact Atlassian Support directly, or ask your organization admin to open the request on your behalf.

If you believe the related JAC issue should be reviewed or reopened, the usual route is to raise it through Support so they can escalate it internally to the relevant product team.

@Gabriela , I do not think your answer applies in this case, as the user has already confirmed during question creation that they are on a Premium subscription.