Mikael Sandberg Community Champion

This is happening because you are using External account types, and in order for that to work the user has to first confirm their email address (they will get an initial email with instructions). Once that has been done they will be able to submit requests via email. If you disable the External account type and only use…

Short answer is no, currently you cannot have multiple boards in a JWM project. Your current option is to use the filter option on the board to see issue for specific assignees/reporters.

@Charlene Freeman Welcome!

Hi @noa einhorn, Welcome to Atlassian Community! You may want to take a look at Atlas, it allows you to report the project status on a weekly basis.

Something like this should do it: In this example I'm using the labels field, but the principal is the same for your use case.

Hi @Ryan_Smith, Welcome to Atlassian Community! The way I would create the automation would be to use the Field value change trigger and use the issue fields condition to check it the UX/PO/QA Approval field has all three values and if that is the case then transition the epic.

Hi @noa einhorn, Welcome to Atlassian Community! If you are on JWM Premium plan then you can create an overview that shows all issues form the selected projects. The other option would be to create a board in a JSW project and change the filter to bring in your JWM projects to it.

@Andrey Miranda Diaz You need to have a Jira Software project in order to do this, then just go to that project and create a new Kanban board and base it on an existing project, which in this case would be the JSM project. 

You could work around it by creating a board in a JSW project and change the filter so it includes issues from the JSM project.

Currently Boards in JSM is a Cloud only feature. There is a suggestion to have it added to JSM DC, see JSDSERVER-13977, that you can vote on and follow. 

Hi @Iain Brocklehurst, Welcome to Atlassian Community! In order to remove it from the sprint you need to go to the issue detail view of the epic and then clear the field Sprint. 

Here is what you get if you search on field security.

Yes and no, default Jira does not have field level permissions, so you would have to get an app from the Marketplace that allow you to set permissions on fields.

Default JQL can only use the parentEpic and you have to know the issue key for it. If you want to do a generic query like get all epics in a specific project and all children, then you would need an app from the Marketplace that either extends JQL, like JQL Tricks or Enhanced search. The other option is to use JXL, since…

Hi @Glenn_Merritt, Welcome to Atlassian Community! You would have to create a new field configuration scheme that is specific for the project in question. I would start by copying the existing one and then just go in and change the field to be optional instead, and then assign the scheme to the project. You can learn more…

Go to the project in question, then go to Project settings > Permissions. From here you can see who has the ability to assign issues and change the permission scheme if needed. Please note that if the permission scheme is shared across multiple projects and you change the permission it will affect all projects that is…

As the error message indicate, you have to make sure you have assign issue permissions in the project that the issue belongs to. Most likely you have to be added to a role in that project that have the right permissions.

No, there is not other option to it.

The short answer is no, you cannot configure the filter used by the board in a JWM project, even if it is a company-managed one. There is a suggestion that want the same customization as in JSW, see JWMCLOUD-423, that you can vote and follow if you like. 

Hi @Michael Hibberd, Welcome to Atlassian Community! Check the filter that is associated with the board, if it is to broad and spans multiple projects you need to have sprint permissions in all those projects. For example if the filter looks like this: components = something This would mean that you would need sprint…

You would have a user who's email address is a distribution list and set that user as the one to be notified.

You could add a Lookup Issue component that looks for similar issues and only if the size returned is 0 then continue to create then new issue. I have a similar rule that closes duplicate issues if the lookup issue finds 1 or more issues with the same Id in the description:

@Andrea Ringgenberg I have to disagree with you that you cannot move tickets from the board into a queue. Queues are just filters that you associate with a specific queue. The board would show all tickets that you have in the project, while a queue can be very specific, for example only show email requests.

Hi @Catherine Newstead, Welcome to Atlassian Community! Since you are mentioning sprints I am assuming you are using Scrum board, and there you cannot disable the backlog since that is the default functionality for Scrum boards. The backlog can only be disabled if you are using a Kanban board, which does not have sprints.…

Hi @Mathieu Destrempes, Welcome to Atlassian Community! You would need an app in order to do this, there are couple of them in the Marketplace that can give you the velocity based on the user. We evaluated Individual Velocity Report/Chart Dashboard a couple of years ago and it worked fine.

Hi @Andrea Ringgenberg, Welcome to Atlassian Community! No, backlog is not a feature that is available in JSM, the only thing you can enable is a Kanban board if you want to work that way instead of using the queues. This can be enabled if you go to Project settings > Features and under the Feature lab section you should…

Here is part of what it looks like, I have an if/else component for each approver group that needs to be added so they all look the same: Because I am using the user attribute in Assets I can just paste the approver directly in to the field, since the value returned from Assets is their Atlassian Id.

Based on the description the integration only allows for creating and removing users, not syncing tasks between the two.

Hi @Rita Fahed, Welcome to Atlassian Community! It looks like Factorial has an app that you need to install on their end in order to integrate it to Jira. Here is the app, https://factorialhr.com/apps/integration/jira 

Hi @Manja Vogel-Kautz, Welcome to Atlassian Community! No, you cannot remove those users, unless you have removed the app. If you remove the user that will affect the functionality of the app. The level of permission needed is dependent on the app, when you first set up an app it usually tells you what permissions it needs…