Belto Atlassian Team

If you're experiencing any issues from third-party apps, please see JRACLOUD-92775 - Broken connect apps nested pages on instances with new navigation

Thank you for confirming. Indeed this method does not apply for the new enhanced board experience. I've sent this feedback to our product team to make sure they take this into consideration.

Hi @Darrel Jackson , I verified on a test site and I see that hovering over the ••• still provides the URL with sprintId at the bottom of the page. Could it be possible that you were looking at a team-managed Board? This method is only applicable to company-managed Boards.

Hi @Steven LeVine - In its current state, there's no public audit for admins to view when users are suppressed and would indeed have to rely on users informing them that they haven't received an email. This change is just one step in the work that needs to be done as it continues to improve. You should be able to track…

Hello Stelio, We recently took notice of this and raised this bug JRACLOUD-80097. This is a backend issue that occasionally fails to retrieve the statuses and displays that error. But as you pointed out, you are still able to proceed to create the issue however you won't be able to set the status during the creation. When…

Hi Ravikiran, It sounds like there is most likely a group that was added to the Issue created event in the Notification Scheme of that project. You should head to the Project settings → Notifications and verify what the notification is configured. Check out Configure notification schemes for more details.

Hi Juncal, There's a feature request for this but unfortunately, there are no workarounds available. * JSWCLOUD-6034: Velocity Chart should show all Sprints and not be limited to last 7 Sprints Cheers, Belto.

Ahh, I see what you mean. You're referring to Create issue in epic outside of the Plan directly on the Epic issue in Jira. The answer unfortunately is still no, it isn't possible to disable this. The reason being is that the "hierarchy levels" is a feature and structure that is only respected in the realms of Advanced…

The rule would look somewhat like this

Hi Dave, If I understand correctly you want to disable to create + Create issue option for the Initiative level? This isn't possible as this is tied to the Create Issues permission. A possible workaround would be to isolate the Initiative Issue type to its own Workflow Scheme and add a validator to only allow certain…

Hi Eric, This is happening because issues on the Story level (in your case Task) do not use the Parent Link field you're trying to update. This particular field is used in conjunction with the Hierarchy settings from Advanced Roadmaps and is only applicable for issue types above the Epic level. Though you may be able to…

Hi Sean, If you suspect that the user has been added to a block list I recommend contacting our Support team at Contact Support as they would be able to verify this and remove the suppression. Cheers, Belto.

To learn about column configuration see Configure columns for company-managed projects 

Hi Martin, It sounds like you're looking to create some custom fields using the Select List (cascading) field type. Here are some links to help you get started: * Create a custom field * Custom fields types in company-managed projects - Select list (cascading) Cheers, Belto.

Hi Akshith, These guides should help you out with that * Flosum & Jira Cloud * Jira Integration with the Flosum Solution Cheers, Belto. 

Hi Karl, This could be related to the grouping you've applied on your Plan. Please have a look at Issues appearing in the Unassigned swimlane when Grouping by... Cheers, Belto.

Assuming that the Bug in ST is being linked to the BT issue, you could use a Branch rule in Automation for Jira which would allow you to pull information from linked issues * Branch automation rules to perform actions on related issues

"What's gonna work?...Team work!"

Great tip Melissa

Finding a way to disconnect yourself from your devices after work hours really helps with this. Great article @Jenn Velázquez 

Great tip @Jack Brickey 

Thanks for sharing @Kristen Roth 

Being able to drop on my headphones and get lost in the music, essentially creating my own bubble

The community will always like to meet Atlassians

I'll have to say Thursday since it's "Friday-eve" and gives me a burst of energy knowing that

This is what I imagine it looking like

Reasons this error may occur: * The is no Confluence Space connected to the Project * The user clicking on the Run retro button does not have access to the Confluence Space that's connected to the Project * The user clicking on the Run retro button does not have permissions to create pages in the connected Confluence Space…

This is currently being tracked as a feature request under https://jira.atlassian.com/browse/JSWCLOUD-17758