Mikael Sandberg Community Champion

Hi @Dina Farahat , Welcome to Atlassian Community! You should contact your Jira admins at Vodafone and they should be able to help you. Atlassian Community is mainly made up of customers using Atlassian's tools and we do not have access to customer instances.

Oaky, are you using different screens for View, Edit and Default? If you go to Project settings > Screens you can see the views used by each issue type like this If you are using different screens for each (as you can see above, in this case there are two different screens used), make sure all the fields are available on…

Okay, if you give Service project customers - portal access permission to edit issue they should be able to see the details again. This is the default setting in the permission scheme for any JSM projects.

If you look at the agent view, are able to see the fields from there? If you check your permissions scheme, does Service project customers - portal access have the permission to edit issues?

Hi @Jaqueline Daza, Welcome to Atlassian Community! Have you asked them if they see something like this? The portal will automatically hide the details after the request is submitted, but you can always click on the Show details to see them. 

You cannot search the history with the default JQL (there are a handful of exceptions that can be searched by using was and changed). You would need an app in order to search any field. I know JQL Tricks can do it, but there are other JQL extension apps in the Marketplace that can do it too. 

Metrics is data that you want to display on the your Statuspage, for example: * API response time * Web server uptime * Average time an outbound request sits on a queue * Max time an incoming piece of data sits on a queue before ingested * Average time before first reply on customer support requests * Current exception…

No worries, so this is what the automation would look like: This would run every workday at 9 am and only look at issues in the Awaiting Implementation status (the picture is missing the "" around the status, and if you want to narrow it down further you should add the issue type in there as well...). If there are issues…

I would use the status in the scheduled query and then do a compare between the two dates, like this: {{now.isAfter(issue.Planned Start)}} It will return true if now is after your planned start and you can then add a comment to the change or send an email. 

Hi @Yadav Darshan, Welcome to Atlassian Community! Atlassian support cannot be contacted via phone, you have to submit a request via their website, https://support.atlassian.com/ 

Yes, there is a limit, the lookup issues will only return the first 100 issues that it finds.

@Annicka Rosengren that is a good question, there is a request to have it added, CONFCLOUD-72040. I also know that Atlassian Analytics will have possibility to generate reports with Insight data.

@Richu Ann Babu No, the post function will not be executed, so you would have to take that into consideration.

If you use Automation you should be able to prevent the reopening it the comment body contains "Thank you" by adding an advanced compare like this:

In order to allow external customers to email you need to allow customers to create their own accounts. Please see Set up an open portal for more information. And in the near future you will also be able to allow it of specific domains, see Choosing the right approach to Customer Management in Jira Service Management.

Hi @Sam Yang, Welcome to Atlassian Community! No, it is not a bug, the reason you can only set it to private is because you do not have the global permission to share dashboards and filters. 

Okay, so it looks like you have to encode your email address and token for it to work. I just tried it in my sandbox environment and the validation of the web request was successful

The permission for the Get organizations says anyone can do it, except if you fetch it using the accountid for the users, then you have to be a JSM agent. The 401 error indicate that you are not logged in. Make sure you are including the headers in the web request, like this: The documentation says to use Bearer, but that…

Go to id.atlassian.com and log in with the account you want to generate the token for, then go to Security and from here you can generate it.

Halp is fully automated within a request channel. Adding the emoji is a way for agents to create a ticket from either DMs or in a channel that is not linked to a request channel. And if you enable auto-answers in a request channel you can add answers and set up key phrases that it should trigger on. For more information…

Hi @Hayam Guway, Welcome to Atlassian Community! If you have access to Jira Service Management Premium you can use Atlassian Assist to do this. If you do not have JSM you can get Halp which works with Jira.

You can get the ID via the REST endpoint Get organizations, and then you would have to iterate those orgs in order to find the one the user belongs to using the Get users in organization endpoint. 

Hi @[deleted], Welcome to Atlassian Community! Yes, if you are using an automation to do the assignment, this will happen after the issue is created. You could see if adding a re-fetch issue data to your automation before it posts to Slack to see if that helps. 

Hi @mg.rullier, Welcome to Atlassian Community! The short answer is that you cannot remove the comment field. The comment field will always be added to a transition screen. 

The webhook will only trigger based on the event, you would still have to configure your external script to parse the comment for what you are looking for.

You could do this using the REST endpoint for Get workflow scheme project associations, it returns a list of projects associated with a specific scheme.

Hi @Kevin Gilmore, Welcome to Atlassian Community! You could do this by using a webhook that triggers when a comment is created in a PR. Have a look at Manage webhooks for more information.

Hi @Eidar Tøllefsen, Welcome to Atlassian Community! The short answer is no. At the moment the Insight macro for Confluence is only available for Server/Data Center.

Confluence is using three different permissions, global, space and page restrictions. Permissions on a space is adjusted under space settings, and if you have the right permission you can set page restrictions on who can view and edit a page. View permissions are inherited down to child pages, edit permissions are not…

Hi @NickN, Welcome to Atlassian Community! In order to see Insight for JSM data on a JSW project the user has to have a JSM license. The old Insight used to support it so anyone with access to Jira could see it, but the new Insight limits that to only JSM projects.