Mikael Sandberg Community Champion

Yes, and you have a couple of options to do this. You can use Assets and have it being populated from an external source. Another option is to use one of the apps in the Marketplace that allows you to connect fields to external data sources. I have used Elements Connect in the past to do this.

Hi @Wendy Wei, Welcome to Atlassian Community! Your URL contains an extra 1 in the version, try this one instead and see if that works: https://api.atlassian.com/jsm/assets/workspace/{workspaceId}/v1/object/create 

Hi @Anne Warmer, This should be its own question, but the main reason is that Assets is a functionality that is par of JSM. You are still able to use an assets field in Jira, but in order to have access to it you need to have JSM access.

You can, every user get an Atlassian Id, even external customer. All you need to do is use the Find users endpoint and if you know the email address the call would look something like this: https://your-domain.atlassian.net/rest/api/3/user/search?query=mikael.sandberg@email.com This will return the user's profile including…

Hi @David Bidle, Welcome to Atlassian Community! In order to add users to the request participants field without overwriting the existing ones you have to use the advance option, something like this will do it: { "update": { "Request participants": [{ "add": { "id":"<atlassianId>" } }] } } Note that you have use the…

There is currently no settings in JSM that would allow you to include the header/footer on the Portal. One option to try would be to use Excerpt/Insert excerpt and have your footer on a page. That way you can make the change on one page and it will be updated on all other pages that have that excerpt.

Hi @Daniel Prado Rodriguez, Welcome to Atlassian Community! It sounds like you are part of the subset of customers that got the new space creation flow that was announced the other day. You can read about it here, Testing out a new space creation flow. 

Hi @Vincent Luckmann, Welcome to Atlassian Community! Is the field on the request form for the request (project settings > request types)? Have you also checked the field configuration to make sure the field is not hidden? 

The number of licenses for any apps has to correspond to the number of licenses you have for the Atlassian product, there is no way around that.

Hi @Doug Danaher, Welcome to Atlassian Community! The number of licenses you need for Scroll PDF Exporter is determined by how many Confluence licenses you have. So lets say if you have 100 Confluence licenses then you need 100 Scroll licenses. You can find the cost by going to the Pricing tab on the Marketplace listing…

Correct, and after clicking the all --> done link click Edit in the pop-up window on the right and from here you can remove the screen. After that is done click on Post functions to verify if you have one that sets the resolution. If you do not then just add a new one that sets the resolution.

It sounds like someone updated the workflow and added the resolution screen to the done transition. If you have jira admin permissions you can change the workflow and remove the screen from the done transition and then add a post function that will set the resolution field for you, if there isn't one already. This change…

There is still good use cases for self-transitioning/self-reflecting transitions. I wrote an article about adding approvals to a Work Management project that doesn't have the approval feature (only available in team-managed projects) that is using the self-transition to log the approval/denies.

Hi @Lucia Benito, Welcome to Atlassian Community! The guideline is based on the number of story points that you have committed to in the sprint, and it is required that the story points are set before you start the sprint. If you start the sprint and then add story points the guideline will not be visible. And no, there is…

What type of project are you using, company-managed or team-managed? You will see which type it is in the bottom of the left-hand corner when you are in the project. Please note that issue security is only available in company-managed projects.

Also, did you configure the approval step in the workflow so JSM knows what status to transition the request to when you click on approve/decline? If you click on Edit next to the Include approval step it will show the screen for it.

It will have no affect on existing requests. The only time changing the workflow would have any affects on existing requests would be if you removed statuses, changed conditions and/or validators.

Yes, that is correct, that's is what I was referring to. In the first screenshot you are showing one of the subtasks, but the approvers are set on the new hire onboarding request and you should see the approve/decline buttons on that one if you go to the issue details for it, ITHD-76. Or are you trying to add the approvals…

Hi @michael schofield, Welcome to Atlassian Community! In the workflow for the Pending HR approval, did you enable the approval step? If that is enabled it will add the approve/decline buttons when the request moves to that status, but they will only be visible to the approvers. 

The only thing missing from your screenshots of the SLAs are the start and stop conditions, but as @Gizem Gökçe _OBSS_ mentioned above SLAs do not go back in time to start the SLAs for an issue. Did you set up these SLAs after the requests included in your screen shots were created? Or was the SLAs already there before? If…

Another option would be to utilize Assets, you could then have all your Managers in there as objects and then use an assets field instead, since that does not have the same restrictions that a user picker field has when it comes to restrictions.

Yeah, user picker fields are tricky when you want to restrict the project, since that will restrict what customers can see. The way I work around it in our HR project is that I use issue security instead, that way we can control who have access to specific requests. Some requests are locked down to only allow the People…

Since you are doing external calls via the web request then the error would be coming from that external source, not from within Jira. There are limits, but those limits only applies when you make calls to the Jira API, not external APIs.

That looks correct. If you change the channel access to public, I assume that the field works as expected correct? You may still run into issues on the Form since it does not support group context so it would still list all your users.

Are you allowing your customers to search other customers within either their organization or project? Check your customer permissions under Project settings. If you are restricting this then what you see is expected, since customers, either from the portal or the generic form URL may not have access to view internal…

What does your SLA looks like? Are you filtering based on issue types of request types? If you use the same query in a filter will it include the request that you are expecting the SLAs to pick up? What status is the request in?

Do you know what plan you are on? You picked Premium for the question, and the support page should only redirect you here if you are on a free plan. Did you enter your site URL correctly on the support page?

Hi @Katherine Martins, Welcome to Atlassian Community! You should contact Atlassian support for this and they can help you check and see if your email address has ended up on the suppression list.

Hi @Christine Marsh, Welcome to Atlassian Community! This is expected, guests do not have access to the people directory and therefore cannot use @ mentions. You can learn more about the limitations in this KB. 

Currently this is not possible since the assign issue component in automation only support a single user being on-call at the time. I wrote about a solution to this in this article, you can do it by using IPaaS, in my case tray.io. You could probably do it with just automation, but you would not be able to…