Vijay Dadi_b69v44 Expert

Hello @Kieran Fisher , Never found a solution for this yet.

Hello, I would suggest having one custom field and have one automation with a trigger when issue is trigged. Have edit issue step and copy the current status name to custom field. please try n see if it helps! Thanks Vj

We did build an custom workflow for change management with 4 levels of approvals. Though I was new to JSM, I liked the way how we can build workflows with ease. Vijay 

with this move, endpoints for jira operations and opsgenie are different now. Vijay

There is not such functionality available "from which portal the request has been created". There is a identifier "request-channel-type" which holds values (email, jira, portal). Regards, Vijay

Wowwww...i just made it !

Hello, For every status change, it has its own transition id which you can see it in the workflow. and This will be your request body. API end-point https://xxx.atlassian.net/rest/api/3/issue/<<issue-key>>/transitions Request body: { "transition": { "id": 121 } } 121 is the re-open transition id for my incident. Vijay

want to export only selected (multiple) automations.

try this { "fields": { "customfield_10425": [{{lookupObjects.jsonEncode}}] } }

hello @Nevra Yavuz , If this is the case, you can remove the fields from view screen which are not needed. Vijay

Hello @JZD , If you are importing the linked objects, are the linked objects are already imported before the main assets are imported. Vijay

Hello @Charan , After the user has submitted the request, on the top you will see the issue number. If you click on that, it will take you to the agent screen. Vijay

Hello @Joseph Lam , I would suggest you add more details while posting your questions including screenshots. Vijay

Hello @Krishna Malutummeda , Could you please provide more details on the issue and may be a screenshot would help in understanding the issue. Vijay

Looks like you do not have permission. Try with elevated account access if you have any admin account.

clink on the 3 dots at the end and you will get an option to move them to context field section.

Move them to context fields section, that should resolve your issue.

Hello @Luc Trepanier , Verify if they are added on the issue layout or not. If not, please add them to context field sections and that should help. Vijay

Oops....corrected

Hello @Luc Trepanier For every issue type, you have a separate screen configuration which will include Create, View, Edit, View/Edit. If you are not to see your custom fields on the view screen, add those fields on to your View screen of respective issue type and that should resolve your issue. You have to be admin/project…

@Yatish Madhav , I agree, me myself built many automations/integrations with API tokens using service accounts. But I am happy that it will not affect existing tokens. This will new annual task for the admins. Vj

Hello @Alicia Martínez García , Yes, that is the feasible solution for your use case. Hope it helps ! Vijay

Hello @Justine , If you are a jira admin, you have a capability to write an automation with the trigger as "when object updated". Hope this helps! Vijay

Hello @Alicia Martínez García , If you are using same workflow for different issue types, there is no possibility that you could have different screen configurations. This is because your request types are linked to 1:1 workflows. Hope this helps or someone else has any solutions incase. Vijay

Hello @Fiona Pratt _Sourcesense_ , This is doable. The field where your approval groups/users are stored should be a multiple user/group picker. If the approver details are stored in asset schema, you have to write an automation to do an object lookup and populate the approver fields as soon as the request is…

Hello @sunita gupta , If u understand correctly, you are trying to build a form for your request type and let user choose the approver fo9r their request. If that is the case, add a field on the form and link it to the Jira field (Approver). Associate the request type with the workflow (Service Request with approvals) This…

Hello @Fiona Pratt _Sourcesense_ , Would you please provide the screenshot of your workflow. Also let me know if you are trying put approvals at a single step or at multiple steps. Vijay

Hello @Rudy Hemkes , You can not change the data type of the asset attribute if that field already has values stored in it. There are two ways you are achieve to change the data type of the asset asset attribute. 1. Clear all the values from the current default/text field, then the system will allow you change the datatype…

Hello, If you want to hide these requests from portal, remove them from the portal groups and those will request types will be hidden automatically from portal. Vijay

Hello @Martin Quezada , {{issue.url}} - use this smart value to include the link to the issue url. Hope this helps ! Vijay