Mikael Sandberg Community Champion

Yes, I think setting the permissions on the object schema makes it easier to maintain. I can see where it can be used on the object type level, for instance if you information in that that should only be visible to a subset of users, but I recommend to stay away from it if possible.

Permissions on the object type level can override the permissions set on the object schema level. Have a look at this KB, there is a good example under the Object type permissions vs object schema permissions section. And if you do not set permissions on the object type level, the permissions on the object schema level…

Hi @safder_raza, Welcome to Atlassian Community! I have notified the Atlassian support team that is on here and someone should reach out to you within 2 business days. 

Correct, if that role is not in the security level the customer would not be able to view the request via the portal. Let say that you just added the Reporter, then the only way the customer would be able to view the request would be if they had access to your instance which would require a license.

@Harsha Shridhar there is, but you would need an app from the Marketplace that can display it on a dashboard. Another option would be to use a second custom field that gets updated via automation when your Ranking field is changed. But depending on what plan you are on this could easily make you hit the monthly automation…

Yes, Assets can be used for any type of data, it is not just for Asset tracking. For example, I use it in our HR project to get different approvers based on departments. Another use case that was presented during Team 24 (24 Hour Fitness was the customer) is to use it for delegation, so if a manager was OO for a period of…

Hi @Fatima Mohammed Siddiqui, Welcome to Atlassian Community! As long as Service Project Customer - Portal Access is part of the security scheme it will not affect customers access to the request via the portal. In your case you want to keep that role in your security level and then just make sure for the level that the…

Any copied workflow that is not active (linked to a issue type) are inactive, and if you go to the inactive workflows tab you should see it there.

Just created my submission, https://community.atlassian.com/t5/Confluence-Cloud-Admins-articles/Confluence-Company-Hub-Outreach/ba-p/2868316#M559

And if you are looking for the count you can use Post object aql totalcount.

It is a limitation in automations, yes. Any lookup function in automation will only return the first 100 results it get back. The workaround would be to use a web request and the Post object AQL to get more than 100 objects. 

It is possible, but you would need one of the apps that allows your to use external data sources for custom fields. There are multiple ones in the Marketplace, I have used Elements Connect in the past to do this.

Hi @홍신영, Welcome to Atlassian Community! Since the lookupIssues only return the first 100 issues that it finds, your only option would be to use the Count issues using JQL endpoint, both for the total and for each priority. So basically your automation would have 6 different web request components to get the totals.

So in your workflow you need to set the resolution on the transition to Resolved, and you do that by adding a post function. For existing requests that are in Resolved status you can create a scheduled automation that sets it. This KB mentions that you can add a transition in the workflow to set the resolution on existing…

This would only be possible if you use either Forms, or an app like Scriptrunner or Power Scripts which allows you to change the UI. I think Power Scripts will have Live fields soon, that is what I used on DC in order to show/hide fields. There are also other apps in the Marketplace that can probably do this.

Hi @guy_geoffroy_ayadokoun, Welcome to Atlassian Community! What you see is expected, team-managed projects are like an Island without access to anything outside of it. In order to get the custom fields to come over you would have to export your issues to a csv file and then import them in your business project, that way…

Correct, the customer notification will aways contain a link back to the request on the Portal. Sure, you could turn off the customer notifications and use automation to send the response to the customer, but you would then consider how many tickets/replies you have so you do not hit the automation limit.

Hi @Fatoumata Oulare, Welcome to Atlassian Community! You would need an app in order to do that, something like Confiforms or any of the other forms apps in the Marketplace. Your other option would be Jira Service Management.

If you go to Queue settings > Priority groups and click Manage queues you can re-order the queues by clicking on the dots icon on the left and move the queues around.

Also check the comment component, by default the "Prevent duplicates by only adding this comment once to a particular issue." option is selected which would explain why it worked yesterday but not today.

In your workflow, does the transition to Resolved set the Resolution? Either as a post function or a screen with the resolution field on it so the agent can select the resolution? My guess it is that the resolution is not set and that is why requests that have been moved to Resolved are not removed from the queue.

Hi Ellis, Welcome to Atlassian Community! No, you cannot turn off the Portal, that is a major feature of JSM. But what you could do is hide all the request types from the portal so the only thing the customer would do on the portal would be to see their submitted requests.

I would use post function and the notification scheme over automation if your are running close to your limit. Yes, the notification scheme is more limited in what you can do with the email, but you do not have to worry about any limits when using it.

Automation now support nested IF/ELSE conditions, so you could add one IF for the first condition and then in that one add another IF/ELSE for the other two fields. I was trying to find the announcement about it, I thought it was an article here on the community but are not able to find it right now...

Hi @scrivanosilvio, Welcome to Atlassian Community! Short answer is no, manual automations cannot be triggered via the bulk change. Bulk change would only trigger automations that act on field changes/transitions. 

Correct, Assist or the Virtual agent cannot determine permissions based on the user in Slack/Teams.

The summarize button has moved to the bottom of the page on the right hand side, and you will see that if you scroll down to the comments section it can now also summarize the comments.

Forward it to https://www.atlassian.com/trust/report-abuse and the team will deal with it. 

You can use remaining() to get a list of requests that will breach within a given time, something like this: "Time to Resolution" < remaining("1h") This would return the requests that are about to breach within the next hour.

Hi @Trey Whitfill Welcome to Atlassian Community! The Teams field is a system field and is controlled by the new Teams option that you see on the main menu. In order to add a Team you go to Teams > Create a team and follow the on-screen directions.