Nikola Perisic Community Champion

Hello @Shefali Tayade What you are looking for is to create screens, screen schemes and issue type screen schemes. Screens * Navigate to Settings > Issues > Screens * Copy some of the screens (best practice) and then remove the fields and also rename the screen so it has the name of your issue type: example - PROJ:…

Hello @[deleted] the issues that are not in the Done status will move to another sprint until they have been resolved.

Hello @Ashok Shembde , no. User either can be activated or deactivated. Each user is assigned to their specific Atlassian account which is based on different IDs'.

Glad to hear @Banu Priya . If you found the answer helpful, please mark it as accepted so other users can refer to it easily.

Welcome to the community @Peter Bailey ! Do you have any automation rules set up? Usually, this is something that shouldn't happen. Even if you reply to the request.

You can then go with team-managed Kanban board. It is meant for smaller teams, easy configurations, and no need to have Jira admin to configure the schemes.

Welcome to the communtiy @Enrico Augurusa ! This is because your account wasn't active for some time and Atlassian has deactivated it. In order to solve this you need to place a support ticket here

Hi @Pears Whims , changing the project key doesn't affect the current issues and all of the old links from an old project key will be automatically updated.

It was a temporarily issue. Good to know that it works.

Welcome to the community @Robert Schneider In my experience, we have indeed used Jira for specific reasons of project tracking. This indeed included the both development tasks and bugs. Both were documented and we knew what was going on in the project. Who was the assignee, what was the status of the issue. If it was for…

Welcome to the communtiy @Eva Have you checked the space permissions of that space, if the users are indeed able to view the pages? Have you checked if there are any restricted pages for these users as well?

Hi @Osama Al-Areky There is a workaround of bulk editing the issues where the assignee is changed. * Navigate to Issues section of your project and click on three dots and choose Bulk change issues * Click on Edit issues and choose the Assignee Automation rules would work from the moment when you have created the rule and…

This article should help you understand the CFD better: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-cumulative-flow-diagram/ The more statuses you have, the diagram will be bigger. Which is not something that is practical.

Welcome to the community @Susanne Brandt ! You can set up an automation rule that would look something like this: * Trigger - Scheduled on every 2 weeks (you can specify a different day) * Condition - Issue fields condition where status is one of - here you need to specify your status * Add comment to the issue - here you…

Hello @Thomas Schenkel 1. Usually it is recommended to have less statuses in the workflow to make them easier 2.Green status in a CFD (Cumulative Flow Diagram) or burndown chart typically signifies a task or item that is completed or done. This color coding helps visually represent the progress of work over time. CFD…

For this you would need to have the global automation. Ask your admins to do these modifications for you.

You can follow the guide from here: https://docs.adaptavist.com/sr4js/latest/scriptrunner-migration/migrating-to-or-from-cloud/migrate-from-scriptrunner-for-jira-server-dc-to-cloud It is recommended to use the Atlassian cloud assistant.

Welcome to the community @Priya Pandey ! The automation rule has two scopes: either for one individual project or globally. Just replicate the automation rule from one project to another, since you don't have the option for global automations.

Hello @Shefali Tayade You would need to navigate to settings (on the right stop corner of your screen) > Issues > Issue types > Create new issue type > Select standard issue type. Once you have created an issue type, then you need to add to the issue type scheme. Find the name of your project, click on Edit, drag and drop…

Welcome to the community @Mano Chitra ! Even if you do migrate the scripts, almost none of them will work because ScriptRunner for cloud works only based on API's. Groovy scripts are not supported on cloud.

Hello @Marcel van der Vliet Have you tried exporting in incognito mode and also clearing your cache that contains atlassian.com . If the error still persists, check the browser development console for any of the errors and what are their codes. If you above everything else issue still exists, raise a support ticket for the…

Hello @Purnendu Chavan You can apply some certain permissions for attachments: * For creating, delete attachments and delete own attachments permissions should only be granted to Group A * For both teams in order to view the issues they need to have the Browse projects permission which is necessary to see the issues…

Disable the automation rule and test it again.

Have you made additional changes and made yourself the default assignee from project settings?

Hello @Danylo Borodai You can find a good example posted by Atlassian from here: https://codesandbox.io/p/sandbox/strange-fermat-cgobs3?file=%2Findex.html%3A1%2C1-48%2C1

Make sure that your issues have the Team field filled with the adequate team.

@[deleted] The numbers in my query represent the ID of each team. For your query instead of using the <front end team> you should be using the ID of the team. You will get this when you create your team and mention it in your query from your screenshot.

Teams.

Hello @[deleted] Yes, you can. First, you need to create these teams by using the Teams funcionality where you add the members to the team. Then, you need to create three filters: * FIlter which will be the main board - This is the example of JQL query: project = "Company Managed - Kanban" AND "Team[Team]" IN…

Hi @alexandrerosseto Atlassian support needs to take from here, as from the community we couldn't troubleshoot the problem. You can raise a ticket for them here Today, there was an incident of slowness of Jira, reported by Atlassian. Are you still facing this issue?