Mikael Sandberg Community Champion

If you check out the KB it will go more into details about this, and there are also recommendation when you should set up your customers as portal-only or add them as a site user and give them JSM - Customer access.

So customer that are listed under admin.atlassian.com > Users have more permissions then portal-only customers. You could enable other licenses to them, which cannot be done to portal-only customers. It also means that they could go to your site's root URL and also go to start.atlassian.com to log on to your site.…

If you go to admin.atlassian.com and select Settings you should see Atlassian Intelligence listed on the left, and from there you can enable it.

The difference between portal-only customers and users that you give JSM - Customer license to is that portal-only customers are usually external users that is not managed and they cannot log in on your site's root URL, they must use the portal's specific URL. Users that you set up from admin.atlassian.com counts toward…

Hi @Colby Cliffe, Welcome to Atlassian Community! That list is just the available statuses that you can assign to an attribute. In order to set the status on an object you need to have an attribute of the type status and then you select the values that are available for that attribute.

You can't do this with automation, since they execute after the issue is transitioned. What you should do is add a transition screen in the workflow and make the comment field required by adding a validation rule to that transition.

Hi @Courtney Cashen, Welcome to Atlassian Community! No, Cloud does not have a similar solution to the one you found for Data Center. What you could do is add a link as part of the description that give the user more information. Another option is to add a message field with the information by using the Message Custom…

This should do it: { "fields": { "customfield_10167": { "id": "6169cf0d9cdb9300722233ab" } } }

Is the project a team-managed or company-managed? The error you get indicate that you have more than one field called Product Owner and if you are using a company-managed project then you can use the advanced option to set the owner by adding this to the advanced option: { "fields": { "customfield_12345": { "id":…

It looks like the screenshot was not saved when you uploaded it...

You may want to update your post and remove the URL, this is a public forum and most of us here are customers just like you and do not have access to other customers instances. If you can post a screenshot of the error that you get that would be helpful, and also what your rule looks like.

Hi @Gustavo Solato, Welcome to Atlassian Community! You will not be able to set a calendar for when the automation should run, but you should be able to use a lookup table that has your holidays and then use smart values to compare the current date with the table to see if the automation should continue or not.

Yes, that is possible and the API endpoint that you can use to get that information is Get space permissions, it will return the permissions for the specified space and you can then filter out the groups from it. 

It could also be a field that is fed by Assets, but you would have to check with your Jira admin regarding this. The community do not have access to customers instances.

Person info is not a default field, so your Jira admin must have created that. My guess is that it is a user picker field and if that is the case then the reporter needs to have an account on your instance, not just as a customer, in order to be listed in that field. Again, this is assuming that the field is a user picker…

The short answer is no, currently it is only Jira admins that can change global automations (automations that has a scope that spans multiple projects). Atlassian is working on making the admins permissions more granular, so hopefully this is something that is considered too. I did a quick search but could not find a…

Hi @Joseph Medina, Welcome to Atlassian Community! Have a look at this question, it describes how this can be done using automation. Basically what you do is getting the hour when the request is created and then use the if/else condition to assign using the balanced workload based on the hour. Another option would be to…

I don't work for Atlassian, I am just a customer just like you. But I think this might be based on the customer permissions too, since you can set it so the customer can share the request with anyone.

I don't think the Approvers field can be restricted, and I don't think that you could use a custom user picker field since you would need Browse users and groups global permissions which cannot be assigned to portal only users. The only workaround that I can think of, besides not allowing your customer to select the…

You might be able to do it with an intent that asks the questions that you have in the form and then update the issue that way. The questions would be coming in as comments, so you would have to use automation to extract it and then either add it to specific fields or just add it to the description.

Here is one suggestion to add support for forms, JSDCLOUD-13190, I would recommend you go and vote on it and watch it. 

Hi @David Willoughby, Welcome to Atlassian Community! This is expected, the Virtual Agent does not support Forms at the moment, so you cannot use request types with it that has a Form attached to it. There should be a suggestion for it, let me see if I can find it. 

I think you are confusing Jira Service Management (JSM) with Jira Work Management(JWM). If you have licenses for Jira Software then you will also have access to JWM, which was announced in this article. JSW does have their own kanban/scrum boards and in order to get access to project plan in JSW you would need to be on the…

Yes, it can be done using the REST API. You can get the all the information you are looking for by getting all the projects and then for each project use Get project. The response from Get project will have both the project lead and the category it belongs too.

Yes, you can add/edit resolutions. You need Jira admin permissions and then go to Settings > Issues > Resolutions. From here you can edit existing values and also add new ones.

By default the permission scheme for a JSM project uses the Service Desk Team project role to give users that have a JSM license access as an agent to that project. So if your permission scheme is using a group instead then yes, that would be the way to go. But you would get an error message because JSM is expecting that…

Hi @Ashvin Parihar, Welcome to Atlassian Community! In it's simplicity the automation would look something like this:

By default anyone that have a JSM license and are added to the Service Desk Team would be an agent in that project. It is only if you have a Jira Software/Jira Work Management license and are added to the Service Desk Team that you become a collaborator in that project. In order to add users with JSM license as…

It is possible, but it would require an app in order to do it. There are a couple of apps in the Marketplace that can do this, our engineering teams have been using Time to SLA for a while now and they are pretty happy with it.

That is expected, since boards are not project specific, they are just located within a project. And yes, you can create a board after the project is created and make that board located in it.