Marc -Devoteam- Community Champion

Hi @Chance Douglass I'm not sure but are the agent responses JSON, I think they are text. Do you get results, when using {{agentResponse.documentStatus}} or even simpler {{agentResponse}} What are the responses?

Hi @Vinnasoft Welcome to the community. Ootb this is standard functionality. If a sprint is being closed there will be a question what to do with the remaining open work items, bring them to the next sprint or place them back on the backlog.

Hi @Chandrashekhar Maruti Badar Can you provide the output of the web response here, this i=to see how the output is presented. This could help us members to possibly help you out.

Hi @Matt Richards This is only possible when you have a JSM premium or enterprise subscription. Free and standard tiers of JSM don't support this integration. This is also stated on the documentation page you are mentioning.

Hi @Juan Angel Saenz Welcome to the community. Start by setting up a company managed JSM project and go over the working. See documentation; https://support.atlassian.com/jira-service-management-cloud/docs/what-is-a-service-project/ 

Hi @Jasmin Koolipurackal See delete-an-atlassian-organization , this will also include articles on deleting products (apps).

Hi @Jasmin Koolipurackal AS an org admin you can grant yourself access to those instances and then remove the apps on the instances and remove the cloud instance.

HI @Marija Aleksejeva Set the JQL for the scheduled triggers as follows Status = "Waiting for customer" AND (updated <-1d OR updated = -2d) Status = "Waiting for customer" AND (updated <-2d OR updated = -3d) Status = "Waiting for customer" AND updated <-3d 

Hi @[deleted] Not a Jira admin, you need the org admin (that is the admin of the Atlassian Cloud overall) This can only be done via Atlassian Administration.

Hi @Naoki The AQL on then custom field context should be working: objectType = "Laptop" and userInAssets."Atlassian Account ID" = ${reporter}

Hi @Claudia Riverin Please accept my answer as a solution, if my answer helped to solve your request. This will help other community member trying to solve the same. P.S. If the answer is very valuable to you, please share some kudos.

Hi @Marcel Hager Use the cardinality option to set a minimum value number as 1. This will set the attribute as mandatory on creating an object.

Hi @Anders Rosén In your automation, create a variable. Call this variable version and set the smart value to {{version.id}} In de web request custom date set the id to: "id": "{{version.id}}

Hi @Myles Boyd You can, see in the article I shared to set the portal to be available to anonymous access. If this is not an option for you, then yes they need to have an account on the portal, or create their account on the portal.

Hi @Mohammed_Zeyad Yes, this should work. Also see this KB article on the email action to list all found issues per reporter and list them in a single email. https://support.atlassian.com/automation/kb/automation-rule-to-send-single-email-for-all-issues-per-assignee-due-next/ 

Hi @Vincent Ong No you don't need to be Jira Admin. Any Organization that you create can be used in any JSM project.

Hi @[deleted] Only an Org admin can delete products. So you need to find who is an org admin in the Free Cloud instances and ask them to retract your permissions.

Can you show: 1. what type of project is this (e.g., company-managed, team-managed, etc.), 2. images that show your complete rule. 3. images showing the details of any relevant actions/conditions/branches. 4. images showing the Audit Log details for the rule execution. 5. Explain where the issue is. These questions are not…

Hi @Anders Rosén Welcome to the community. This works fine in postman payload example: Custom data: { "description": "Version was released on {{now}}." } Result is "Version was released on {{now}}.", this as description is a text field.

Hi @Mohammed_Zeyad Welcome to the community. You need to place the lookup issues action within the Branch. Then based on reporter the issues will be searched.

Hi @Myles Boyd To recored responses, any email address replying on an issues need to be registered (log in). This can be changed, then you need an open portal where any user can reply or raise an issue without logging in. See the section "Set up anonymous access to help centers and portals on your site" in this KB article…

Hi @Vincent Ong See this KB article for solving this. Your Org admin has to execute this. https://support.atlassian.com/jira/kb/add-organizations-button-is-not-visible-under-customer-section/ 

Please accept my answer as a solution, if my answer helped to solve your request. This will help other community member trying to solve the same. P.S. If the answer is very valuable to you, please share some kudos.

Hi @Vincent Ong Can you provide screenshots, for calcification? Has the admin disabled and enabled the feature? The setting, has to be like this:

Hi @Dominik Hebestreit So your option is to create a setup using the API or manually. But as it's only internal, why would you want to limit transparency within the company. On issues spanning a store, you can't select multiple orgs, then you would still need and org where everyone is in. But that's a decision to be made,…

Hi @Sujeet Pathak - Amoeboids The function in DC is as designed. As mentioned, this function worked in Cloud as well, but on Cloud this has changed,

Hi @[deleted] Welcome to the community. I don\t understand your question, can you elaborate and provide details on the isse?

Hi @Sujeet Pathak - Amoeboids This is as designed by Atlassian in the latest issue view, in the previous issue view, this could be done. See also; JRACLOUD-72060 

Hi @Bhattacharya_ Sumita Welcome to the community. There has been an active incident, relating email delivery. https://jira-software.status.atlassian.com/ This should be resolved now.

Hi @Dominik Hebestreit You can setup your orgs and then add a mail domain to on org, and use automation to add users to the right org. Or by use of automation create and org based on the mail domain to customer is using. You will need to start somewhere. Also big orgs usually don't use orgs, they don't want other customers…