Nikola Perisic Community Champion

Hello @David Woodhead , a lot of users are having this error. Do this again but in incognito mode.

Hello @Devendra singh , have you checked when you click on 4 dots on the left sidebar? When you got Atlassian Administration and go for Apps, do you see Confluence? If everything is there, run in incognito and clear the cache?

Hello @Rainer Maximini * Which SCIM are you using? * That type of a field this is in Confluence and Jira - user picker? There isn't a direct API for the custom field specifically rather for the issues: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-fields/#api-rest-api-3-field-get

Hello @Christian Wolf Assets are part of the Service Collection along with Jira Service Management,Assets and Customer Service Management.

Hello @Pinar Dogan , for all billing related issues, you can go here: https://www.atlassian.com/company/contact/purchasing-licensing#/

Hi @Tirupal Reddy Indireddy Did you compare your request type forms? Are those mandatory fields system or custom field types? If they are custom field, are they linked with a Jira field?

Hi @sarthak agrawal In the documentation it was not stated that this is for the Atlassian guard. Where did you find that information?

Glad it worked @Matt Hakimi ! Kindly accept my answer so others can refer to it.

Welome @Vishwa Ranjan Kumar Clear your cache and start in incognito mode. Let me know if it worked.

Hi @Matt Hakimi Have indeed tried with cache clearing and incognito mode? Since this behavior is occuring for some issues and for it's not, the problem lies in the backend which Atlassian handles.

I would like to opt in, especially for vibe coding Forge apps.

Hello @Damian Kowalewski For your JSM project, you need to add Due Date field to the screen that is tied with your request type:https://support.atlassian.com/jira-service-management-cloud/docs/add-a-new-custom-field-to-a-project/

Hi @sarthak agrawal No, the audit log is limited to organization admin level only to prevent other users to access this data. The link for the API could be found here: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-group-users

@ProStaffOne This has been happening to a lot of people lately from the community.Your best option is to contact the Atlassian support: https://support.atlassian.com/contact

@Arkadiusz Wroblewski Could be possible, there are multiple problems

Hello @ProStaffOne This problem exists for some time now. Have you tried in incognito?

Hello @Katerina Valouchova This page can help you to see what are your options: https://www.atlassian.com/migration/plan/upgrade-to-data-center-guide#upgrade When you scroll down there is an option of Talk to an expert.

Hello @gollapudi sidhvi * Approval step setup would be useful here - you specify this on your workflow status * If one approver is not available, another approver has to be able to approve or decline the ticket * When the user is on the leave, you would have a new custom field called PTO or something else - if the user is…

Hello @Ricky Blunda You would use JSM and also modify the request groups where as the end result you would get this: For your request types, you need to create new ones that would look like this: Direct hierarchy except work item hierarchy that is applied across whole Jira doesn't exist in JSM. This would be the…

Hello @oranos dawar Deleting your account and deleting your organization are two different things: * To delete your account, follow this link: https://support.atlassian.com/atlassian-account/docs/delete-your-atlassian-account/ * To delete your organization, follow this…

Hi @sarthak agrawal You need to be an organisation admin to be able to access the audit logs. When you, you need to be in Atlassian Administration -> Insights -> Audit Logs

You are welcome @Kathy Dickason !

import com.atlassian.jira.component.ComponentAccessor import java.sql.Timestamp import java.text.SimpleDateFormat def newMilestoneField = getFieldByName("New Milestone Due Date") def commentField = getFieldById("comment") // Current value in the form def currentMilestoneDate = newMilestoneField.getValue() // Original…

Hello @Kathy Dickason This can be done with ScriptRunner behaviors, where you are adding the script to Due Date import java.sql.Timestamp import java.text.SimpleDateFormat def dueDateField = getFieldById("duedate") def commentField = getFieldById("comment") // Current value in the form def currentDueDate =…

@Mohammad Itani You can see these articles: https://support.atlassian.com/jira-service-management-cloud/docs/start-shifting-from-opsgenie-to-jira-service-management/ https://www.atlassian.com/software/opsgenie/migration There are all answers to your questions detailed on these links.

Hello @Mohammad Itani * Are you migrating from one system to Jira? * Are you migrating from Jira data center to Jira cloud? * Are you migrating from Jira cloud to cloud?

@Kaja Iske {{issue.description.toDate("yyyy-MM-dd'T'HH:mm").setTimeZone("Europe/Vienna").jiraDateTime}}

@Albert Manuel That is a different thing then. When AI becomes active on the site, it becomes available for all of the users. Agents are the only ones that can be limited.

Hello @Albert Manuel Each Rovo agent, even the out-of-the-box ones, have the ability to restrict users. To do this, navigate to your agent, click on Edit agent, choose Users and permissions. There are two roles Manager and Editor. Editor has full rights, which are even editing the agent itself.

@Kaja Iske Then you need to adjust your smart value to: {{issue.description.toDate("yyyy-MM-dd'T'HH:mm").convertToTimeZone("Europe/Vienna").jiraDateTime}}