Mikael Sandberg Community Champion

The product switcher is based on the Atlassian products that your instance subscribes to, the only customization you can do is add your own links. If you look at this question it looks like Atlassian is/was interested in understanding how people in large organizations are using the switcher, so I would email Magda and see…

Hi @Alex Billings, Welcome to Atlassian Community! Those two default policies are expected, one it for the local user directory (for users that are not synced from idP) and the other one is for your synced Okta users. Each user directory can have multiple policies and the default indicate one Atlassian should add the user…

You can add multiple mail handlers, but if you use the one that comes with Jira then it will only allow you to use it for one project. If you want to use incoming emails for more projects then you would have to set up external ones either via Google or Microsoft.

There isn't a way of doing it in the UI without going into each project to see if there are issues linked to versions or not, and I didn't find an app when I did a quick search in the Marketplace. You can do this via REST API, the Get project versions endpoint response will tell you the number of issues linked to it.

Hi @Valerie Parra, Welcome to Atlassian Community! Jira Software does have an incoming mail handler that can create and add comments to issues. The difference between that one and the mail handler that JSM is using is that for JSW you can only have one email address for the whole instance, in JSM you have an email address…

@Aleksandra Leesment This should be its own question with a reference to this one. If the information is kept in Assets then all you have to do is use the lookup objects action and then act on the returned result. 

Hi @Cagla Ozardali, Welcome to Atlassian Community! This is expected, since Slack wants the display name in Slack, which by default is firstname.lastname. Your other option would be to import the member Id as an user entity and use that in your automation. Have a look at this article on how you can import the member Id…

This is expected behavior, the approval process overrides any validators that you have on the workflow for those transitions. Based on this suggestion, JSDCLOUD-6988, Atlassian is adding new feature request to add a comment as part of the approval. 

Add a create variable component to your automation, assign the sprint Id to it and then you can use that variable to set the sprint like this:

Hi @Mike Tajik, Welcome to Atlassian Community! You are correct, in order to be able to change the Attachment Download Security Policy you have to be on the Standard plan or higher, on the free plan this cannot be changed.

No, the screenshot I included is creating a task in a JSM project, but as you can see and like Trudy mentioned, the editing of the request type happens after the issue is created. That is what the Most recently created issue branch is all for. So the automation first creates the issue, then the branch will open that issue…

Hi @Benjamin Szwimer, Welcome to Atlassian Community! Those are just the preset values that are available to the automation. It will not show any sprints that you have on your board since the automation is not aware of the boards within your project. But you can always set the sprint using smart values similar to this:…

Hi @Elizabeth Butler, Welcome to Atlassian Community! At the moment you cannot customize the summary page. Here is a suggestion to allow that, JWMCLOUD-242, and I would suggest that you go and vote in it. 

Okay, since you do not see Settings > Issues that means that you do not have Jira admin permissions, and that would explain why you also do not see the pencil when going to Project settings > Workflows. Without Jira admin permission you will not be able to edit workflows.

Hi @Cole Thatcher, Welcome to Atlassian Community! If you have Jira admin permissions you should see a pencil under Actions when you go to Project settings > Workflows that would allow you to edit the workflow. Another way to get to the workflow editor is to go to Settings > Issues > Workflows and locate the workflow from…

Hi @Mark, Welcome to Atlassian Community! The free plan does not allow you to set permissions, that feature is only available in the standard plan and up. 

To set the request type you can do it using the most recently created issue branch like this: Since you said you only have a single request type associated with the issue your other option would be to use the default request type feature instead and not set the request type in the automation. 

Hi @Brydon Parsons, Welcome to Atlassian Community! Yes, we have multiple landing pages in Confluence for this. Our main space/page used to just be links to other pages within Confluence but we decided to redo our IT one and move away from using the portal that comes with JSM. As part of this change we decided to get…

Here is the automation that I have in place for our benefit email:

The KB you linked to is showing the old Home in Confluence. It recently changed and was announced in this article. Your personal space should be visible under spaces and you can also get to it if you click on your avatar up in the right-hand corner and select Personal Space.

Hi @Meriem Amdouni, Welcome to Atlassian Community! No, once the license expire then you will not be able to use that app. 

You have to create your own Slack app, but that is really simple and took me 5 minutes to do. Once you have the app created then you can create incoming webhooks that you can use in automations. The configuration for the Jira Cloud Slack app is not visible, so there is no way of getting that. But I do know that it works…

No, unfortunately there is no such feature. If the issues were from the same sprint it is easy, but if they are from different ones then yes you would have to go into each one to get the previous sprint.

You need to go to Settings > Issues > Custom fields, from here you can create a new user-picker field. Once the field is created you will be able to pick the screens it should be on.

Hi @Andrew Daur, Welcome to Atlassian Community! It can be done in a company-managed project too. You need to create a new custom field that is a user picker field and then associate it with the screens that the project is using. You need to be a Jira admin in order to create the custom field.

Webhooks in Slack is still supported, but you have to create and app in order to do it. Slack has an example on how to do this in their documentation, Sending messages using Incoming Webhooks. I use this for sending Slack messages via automations. 

This is expected, and is related to GDPR. You can learn more about it in this KB.

Yes, the free version will only give you 3 agent licenses, if you need more then you have to go up to the Standard plan. You can find out more about the pricing here.

Hi @Rafael Pagliari, Welcome to Atlassian Community! In order to respond to the customer you have to have a JSM license. So in your scenario if all 10 users need to be able to reply then yes, they all would need a license.

You could do it in bulk, just filter out the issues that are currently in the wrong sprint and then use bulk change to set the correct sprint.