Dave Mathijs Community Champion

Yes, now from Cloud-first to Mobile-first!

Hi @Dharmin Patel , accounts are named, not concurrent.

Hi @Nicolas SARRABAYROUSE Welcome to the Atlassian Community! That is not possible, see: How does the Auto-scheduler in Advanced Roadmaps work?

Hello @Abhijeet Velapure welcome to the Atlassian Community! You'll need the Delete Issues permission to delete an issue, whether it is an Epic, a standard/base issue type or a sub-task. Have you checked the permission scheme associated with the project?

Hi @Leslie Velastegui welcome to the Atlassian Community! Are you a project or site admin? Have you tried the Permission Helper to check the cause of the issue? The projects they do have access to, are those also Jira Work Management projects?

Hi @Iryna Komarnitska_SaaSJet_ can it also calculate the time it was assigned to a custom field value? For a client of ours, we use a custom field "Support Team" and the client would like to know how long an issue was with a specific value of that field (independent from status or assignee).

Looks promising although I'm so used to the default Jira status categories (grey, blue, green) after all these year. Does the app also provide the possibility to add additional status categories and colors?

I never used Betamax, but I used to own my favourite movies on VHS tapes. Our family never had a VHS camera though which is a pity because I like old photos and videos. VHS rentals at the video store, those were the days ... My wedding (long long gone) has been recorded both on VHS and DVD. So happy with Cloud storage now.

Hi @pinkmanChen Welcome to the Atlassian Community! Numbered headings are not native to Confluence Cloud, so you must have been using a third-party app for this. Do you happen to know which Atlassian Marketplace app you're using for numbered headings?

Hi @[deleted] welcome to the Atlassian Community! A task is an issue in Jira. An issue in Jira can only belong to one project. The issue key uses the project key as prefix with a number as suffix. In order to ensure the relationship of tasks between projects, create a task in each of the projects and link them together via…

Hi @Cedric Speer welcome to the Atlassian Community! The Create Jira issue macro is available by typing /create in a page.

Hi Eric, issue syncing between 2 Jira Cloud sites is possible via REST API (custom development) or a paid third-party solution (easier to setup) from the Atlassian Marketplace.

Groups are not pointless (if the permission should apply to all associated projects by default), but in other cases, project roles are preferred. They relieve your work as site admin because you can delegate project access and permissions to your project admin(s).

I understand the use case Markus, but the design of page restrictions just doesn't allow your requirement.

I can confirm that you cannot apply a template to an existing page. Even if a template is used to create a new page, the contents of the page can be changed afterwards so they don't resemble the template anymore. A page template is just a starting point to get you going.

Hi @Slawa Kupermann Welcome to the Atlassian Community! It all depends on the notification scheme associated with your project(s). If all projects are associated with the same notification scheme, and recipients (like reporter, assignee, watchers) are defined for all events (issue created, ...), then all users will receive…

HI @Markus Auberger welcome to the Atlassian Community! Restricted pages can be more restrictive than their parent pages. So unless the assignee of the task has view access to the page, they cannot see the task assigned to them. The solution is to put the task on a page that is not restricted to the assignee of the task.…

Hi @BenWade I understand the confusion. Best practice is to use project roles over groups for more flexibility. * When you grant a permission to a group, it is valid for all projects associated with that permission scheme.* The advantage is that group membership can be done via Active Directory (only when Atlassian Cloud…

Thanks for the clarification @Carol Jang . Can the new name Plans also be applied to the weekly Atlassian Cloud changes blog post?

No, a page move doesn't leave a duplicate, it's not a clone.

Have you enabled the Releases feature in your project? If you are a Project Admin or Product Admin, go to Project settings > Features > Development and toggle on the Release feature.

Now I understand, thanks for the clarification! Well, there are different methods possible: * You could define what success looks like before releasing the feature. Are there any specific goals objectives you want to achieve? E.g. higher conversion rate, improved user satisfaction (review score) * Are you using analytics…

In Server, you have the possibility to create Priority Schemes, selecting only those priorities you need for the project. Create a new priority scheme and only add priorities High, Medium and Low. Then associate the priority scheme with the relevant project(s).

Hi @Danish Akhtar are you able to provide a screenshot of the issue you are experiencing?

Hi @Shawn Lord I see this is an old unanswered question. Were you able to resolve it in the meantime?

@Silva, Lia Please use the Reply field below for your replies instead of the Suggest an answer field, thanks.

I'm afraid not as Priority is a system field and an essential part of Jira. What was your reason to create a custom field for priority level?

Hi @Damico Nicome welcome to the Atlassian Community! Update issue releases The process of updating release details for issues is the same whether they are in the same project or part of a cross-project release. Once you’ve selected your issues: * Navigate to Bulk actions > Release. * In the modal, choose the destination…

Hi @Silva, Lia welcome to the Atlassian Community! Have a look at this KB article: How to hide priority icon in agile board

Hi @Sandra Lawrence , I'm afraid this is not possible without a third-party solution. Maybe one of the other community members has a native solution that I'm unaware of.