Bastian Stehmann Community Champion

Ok, thanks for that information. So you also disabled the Jira Agile-Addon? As I found in this Upgrade-Guide(it is for 7.2 but will probably the same), your Jira Agile must be at least version 6.4.5 to upgrade to a later Version. https://confluence.atlassian.com/jirakb/upgrade-guide-for-jira-7-2-859505724.html So I think…

Hi @LusineTerteryan, the priorities can be edited in the priorities section (Cog Menu -> Issues -> Priorities). In one of the latest release, even priority schemes were added, so that you can have different priorities in different projects.

Hi, you should reach out to the Atlassian Support in this case: https://support.atlassian.com/contact/#/

Hi @Sujata, you will find this information in the audit log within the administrator-gui (Cog-Menu -> System -> Audit-Log).

Hi @Thomas Douglas, your log inlcudes already a hint what the problem is: This error usually occurs when your plugin imports a package from another bundle with a specific version constraint and either the bundle providing that package doesn't meet those version constraints, or there is no bundle available that provides the…

Hi @Michael Jones, maybe it is the problem described here (Issue with encoding) https://confluence.atlassian.com/jirakb/issue-key-increasing-randomly-317196053.html

Hi, you can not do this out of the box, I think. But maybe somebody knows an Add-On that will do.

You can also ask the System Admin to make you the new owner of the filter, then you can change the filter. But if I have a look on that JQL, it is already looking if there is a resolution set. It seems, that you did not set the resolution when closing that issue, if you would have done that, it would also stop sending you…

Hi @David Stokes, welcome to this community. That is no problem. Just create a filter, that selects all that issues. Then create a new board that is based on this filter, and you will have all that issues in that board.

Hi @[deleted], just try jira.permission.comment=denied based on this document https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status

Das liegt dann daran, dass die Spalten im Board einen anderen Namen haben als der Status im Workflow. Auf die Namen im Board kannst du aber auch so nicht zugreifen, dass heißt, du kannst höchstens im Board die Spaltennamen an die Status anpassen, damit das wieder zueinander passt, aber nicht andersherum.

Hallo @Simone Kunz, willkommen hier in der Community. Zu deiner Frage, möchtest du ein Kreisdiagramm auf dem Kanban Board erstellen oder möchtest du ein Kreisdiagramm erstellen, was die Anzahl der Vorgänge in den Spalten des Kanban-Boards enthält? Ersteres geht nicht, letzteres geht grundsätzlich. Da die Spalten im Kanban…

Hi @Nathan Fenner, welcome to this community. You can not change the width of the columns, so your only chance is to reduce the number of columns. Maybe you can either put some status in the same column or you can try to uses more than one board to show only a part of the workflow on each board , for example: * Board…

Hi, this is a snippet from server, but maybe something like this will work on cloud too. def String jqlQuery = 'project=B' def fromProject1 = 'A' def fromProject2 = 'C' def result = '' def changeHistoryManager = ComponentAccessor.getChangeHistoryManager() def searchService =…

Hi @Josh Shelton, if you just want to stop the emails if the issue is done, then you should find the filter (probably "Alert: My Overdue") and change the filter so that issues in Closed status (or whatever status you want to filter out) will be ignored.

Hi @NA, is your problem with Jira notifications or with customer notifications? If it is a Jira notification, please check the notification scheme, if the role author is added correctly to the comment created event. Please have in mind, that a user will only recieve a notification, if the user also has the right to view…

Hi @Dinesh, welcome to this community. Yes, you can. Please have a look here: https://confluence.atlassian.com/jira/changing-the-due-date-input-format-192536.html

Hi @Leo B, thank you for your feedback. I know about linking confluence pages, but it is a big difference between "one click to create a page related to an issue" and "go to Confluence, create a page in the right space, go back to the issue in Jira and add the link (or add the link already in Confluence and then go back to…

Hi @[deleted], welcome to this community. Some Add-Ons allows you to configure, in which projects they will be used, so that is something you could check for the Add-Ons, but if not, I think you will have to disable / uninstall this Add-Ons.

Hi @Yogesh Mude, I think, it is the other way round. The trigger will transition the issue when a branch is created. That is, at least, what also is described in the articles that you link. So if you add the "Branch created" trigger to the "Todo - In Progress" transition, Jira will use that transition when you create a new…

Hi @Leo B, that's some great news, as we have often been asked by our customers for this feature. Do you have plans to bring the "Pages" option also to the server products? Within the workflow, an integration while Requirements Engineering or while documentation would help, as we often do this in confluence and this is…

Hi @Kristiyan Bonev, maybe this is a solution for you. You can create a filter, that selects that issues in that column ( by their status) and subscribe to that filter. Then you will get all that issues by email.

Hi @Karl Weber, you are welcome, great to hear it works now.

Hi @Chethana Hashani, Jira will treat only the issues in the rightmost column as completed. Please make sure, that you have the "Verified" column rightmost and the "Done" column somewhere on the left of that column.

You are welcome. Glad to hear it works now.

Although you just checked that, can you please add a screenshot of the Issue type scheme. And also of the Issue type screen scheme and the referenced Screen Schemes (General, Bug, Epic). I know you just added some of that screens already, but it is easier for me to see it all in one post.

Can you please check, if you have added them to the "Issue type scheme" (in the ISSUE TYPES section on the top of the menu), not in the SCREENS sections.

Do you have added Epic and Bug to your Issue Type Scheme? To delete a project, go to project settings. There is a meu entry delete project.

Hi @Heshan Manamperi, I don't know if crowd supports this out of the box, but Jira for example supports this only in DC out of the box, if you are using Jira Server, you will need an Add-On for this. We have good experience…

Hi @Maja Aagaard, you only need to have one Issue Type Screen Scheme, add there the GJ Bug Screen Scheme for the issue type Bug, the GJ Epic Screen Scheme for issue type Epic and the GJ General Screen Scheme as Default. Then associate this scheme with the GJ project.