Marc -Devoteam- Community Champion

HI @Maksym Mishchenko Welcome to the community. Then it seems that this is bug or Atlassian changed the function. I suggest to raise this at Atlassian Support

The Log work option is related to the the Permission "Work on Issues". If you would remove the permission to everyone, the "Log Work" option is gone. It is not a custom field that can be used for a condition in a workflow.

Hi Julia @ 55 Degrees No as the form is part of a request(s) shown on the portal, so they need to go to the portal. To create a request and fill the required from fields.

HI @Marian Mortell Welcome to the community. Post your question on the Forge developer community, https://community.developer.atlassian.com/c/forge/45 

Hi @Diana Ramirez Welcome to the community. Licenses are based on the number of Jira licenses. Atlassian has no Floating Feature Licensing model.

Hi @Frank Shirvinski As this is a MS function, suggestion is to ask them. Jira MS Teams app provides connection to MS Teams and that is all. You might want to contact Atlassian Support on this, this community forum is not the official support.

Hi @Dennis Thornton Welcome to the community. This might be related to the new "Folders" option in Confluence. My advice is to reach out to Atlassian Support and present them with this issue. I think this is probably currently not possible. Or raise your own request on https://jira.atlassian.com/secure/Dashboard.jspa 

Hi @Frank Shirvinski Welcome to the community. It seems you are askin the for your company environment, reach out to your company admins. This is a public portal for questions about Atlassian products, but not to company specific Atlassian Cloud instances.

Hi Julia @ 55 Degrees Your project has to be anonymously available for customers. If you require users to logon to the portal to create a request, then this is the same form request types using forms. So it is all based on the customer permissions of the JSM project.

Hi @Sneha Raisinghani Welcome to the community. No this is not an option as Log Work option on an issue is related to the permission "Work On Issues" Permissions are can only be related to: * Project Role * Application access * Group * Public * Any logged in user * Single user * Current assignee * Project lead * Service…

HI @RAFIEZADEH Farzad Are showing Jira details on the page? If so, then you need to grant people a license in Jira to have users submitting content.

Hi @Saad Ahmad This import has to be done by anyone having Jira administrator permissions and the steps mentioned by @Vishal Biyani Note, if using status on import the status must exist in Jira and be available on the issue type workflow that you are importing. New statuses can't be created on importing.

Hi @김재훈 _Jaehoon Kim_ The external users wil need to be granted a license. You could add them to a group, then adjust the permission scheme(s) used on the project(s) and grant this group the required permissions. The browse permission is essential, otherwise users can't see the project at all.

Hi @Karen FitzGerald _ICT Programme Delivery_ and @Pasam Venkateshwarrao This will provide the number of sub-tasks counted on each issue. This will not solve the issue to count the number of tasks which. have no sub-tasks as total. Then you would need another automation that runs manually or scheduled an in that rule do a…

Hi mohsen.nasiri@xentral.com Welcome to the community. This is not natively in Jira. You could track this nu using automation. You will need a custom date/time field to store the result Use smart values in automation, see jira-smart-values-date-and-time/#Date-difference And use the creation date and resolved date as…

HI @Karen FitzGerald _ICT Programme Delivery_ You could create an automation rule, that triggers manually or on a schedule. Use a lookup issues action to find all tasks and then make a log action or edit a number field. Both need to have set {{lookupIssues.count}} as smart value in the action. The main issue is that JQL…

Create 2 similar SLA, based on groups. One including the internal agents and one the external agents. Add both SLA's to the same issues, and have similar goals, but based on groups as I mentioned. This will differentiate which SLA will stop counting.

IT could be that the user already has an account on another Atlassian Cloud platform using the same email address. Or the email address has been used before on an Atlassian account. The email also states "jake" instead of "jacob" Based on the screenshot, I see no "lock" icons by the email address or Full name, this tells…

This can't be done in a single click, this has to be set per automation rule.

Hi @Emilia KASPRZYK Sorry, but NO. There is no option for this in an SLA as this is based on an action and not on who doing the action. The only option I see is to add a specific SLA for the external agents, make sure the belong to group. Then set the goal that the issue type is in (a,b,c) and assignee in group containing…

Hi @Eitzaz Haider The solution is that the owner of each rule needs to be the Jira admin. This has to be set per rule. There are no global switches or API options for this. And off course any none "global or "multi-project" rule can be edited by some with project admin permissions and change the rule owner again. Also you…

Hi @Łukasz Zasadziński This can't be reverted, this is due to Atlassian rolling out the new GUI. This will be the new look and feel for every Cloud instance in the near future. See, https://support.atlassian.com/jira-software-cloud/docs/what-is-the-new-navigation-in-jira/ 

Hi @[deleted] No the public name can be set by this user in his Atlassian Profile. There is a feature request fro this so admins can change this, this is currently not possible and only the user can do this themselves. See, https://jira.atlassian.com/browse/ACCESS-905 

Hi @Shi Huang The new users, or the user you want to set as default assignee, have they been granted a JSM license and have they been added to the project and granted the role "Service Desk Team"

Hi @Rob Hearne This iI can't find. You could reach out to the vendor/developer. But the first action they will ask you is to update to the latest version, I would recommend that too. And see if the issue still occurs, is it happening in other browsers as well?

Hi @Maria Melacarne Welcome to the community. As mentioned by @Upasna Bassi this is not possible by using default JQL. There are marketplace apps that provide the functionality you are looking for

Hi @Lisa Medlin There is none, simply as a macro update requires edit rights. The comments section on a page will provide this use case as commenting can be granted without editing a page.

Hi @ISOEH SOC You need to create Teams via the Teams option in the main menu. Operations are based per team.

Hi @[IBM]-Hayata-Kobayashi Is better to place this question on the developer community forum. Forum can be found here: https://community.developer.atlassian.com/ 

Hi @ISOEH SOC Welcome to the community. Within the JSM project settings, is the incident management feature enabled? This will provide the operations section, within the project settings.