Sebastian Krzewiński Community Champion

Hi @MAHAMMAD AZEEM Did you use <> in your url? For me this looks like an issue. Did you try use same configuration e.g. in postman or in CLI? Regards, Seba

Hi @Axel Forsman Please check if account with this email is not suspended/deactivated in your org. Regards, Seba

Hi @Lena Wiethaus Are you able to send screenshot of all validators and this particular validator? Regards, Seba

Hi @Akash Unfortunately at this moment this is not possible to achieve with JSM forms. Your workaround sounds good. IMO - solution like you described should be available in JSM. Regards, Seba

Can you send a screenshot? Looks like your rule is limited to non-JSM project. Regards, Seba

Hi @Satu Rajala Please check this rule - https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112182/. It is not exactly what do you want but you can find a logic about catching customer comment. Regards, Seba

Hi @raj kant prasad You can pick another workflow scheme now only. There is no way to revert changes. Regards, Seba

Hi @Marc-Aurele Brothier I ti si possible with action that you pick. Make sure that users will have permission to modify reporter. regards, Seba

Hi @김선진 Did you ask Atlassian support about that? They have better view in logs so they should be able to tell you more. I requested for their assistance here. Regards, Seba

Hi @Vaibhav Panchal Check if Zoho offers migration tool for that or what input format it accept. If not you can export tickets into csv file but you will lose comments, attachments and ticket history. You can also get tickets via rest api but this require more scripting experience. Regards, Seba

Hi @Olha Yevdokymova_SaaSJet ! Thanks! I will review it and check if this fit to my need. Regards, Seba

Hi @Priyanka Khare ! Thanks for your comment. Unfortunately Dynamics forms and Script runner (I'm thinking about behaviours here) are not working for JSM projects. Forge is not what I'm interested at this moment.

Hi @JG I'm guessing that you are not writing about JSM. IMO: - for notifications 1 and 2 you should use notification scheme - for notifications 3 and 4 you can use automation rule Regards, Seba

Hi @Vera Struckmeier Can you provide more details about this issue in Confluence? Regards, Seba

Hi @Kim Davis Can you tell us more what it is opportunity and account? Those are Salesforce items? Also if you can explain little bit more about this process it will be good to understood it. Regards, Seba

Hi @holger.schaaf Check API documentation if Atlassian didn't change something or ask Atlassian support about that. For me it looks like Atlassian changed something regarding tokens. Regards, Seba

Hi @Gautam Sureshkumar By default it is not possible. Maybe there is a add-on that allows that. Did you consider to use Confluence databases instead of tables on page? As i remember in Conflu DB select value in cell is possible. Regards, Seba

Hi @Antonia Check how those fields are presented in ticket via Rest API. To fix this I would suggest to use .format() function to be sure that all fields have same format. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format--- Regards, Seba

Hi @Antonia In Cloud it is not working like you described, especially in JSM. All fields (excluding Description and summary) will be always displayed on right panel. Fields that will be filled by customer (appear on request form) will display under description. Regards, Seba

Hi @francisco.pineda Yesterday Atlassian had incident regarding it - https://jira-software.status.atlassian.com/ maybe this is still active. Did you contact atlassian support with this? Regards, Seba

Hi @arkadi kaplon It will be good to discuss it with Atlassian. Looks like a case for them. I requested for Atlassian support assistance here. Regards, Seba

Hi @Mariusz Mika As I understand you are on Standard plan now. If you will move your JSM to Premium everything what is built so far will be working. You will get new features with moving to Premium plan. Check plan comparison - https://www.atlassian.com/software/jira/service-management/pricing Regards, Seba

Hi @FS TUNNEL-Equipe Mgt You should be able to hide statuses by renaming it on each form. https://support.atlassian.com/jira-service-management-cloud/docs/customize-the-workflow-statuses-for-a-request-type/ Regards, Seba

Hi @Harold Prestage Fields marked as green are filled by customer on portal form. Fields on right panel (including your red marked field) are fields used by agents. It is not possible to move red marked field into green marked fields. Regards, Seba

Hi @Simon Kolivand As far I know you app license based on your Jira license and you can't buy lower tier. Regards, Seba

Hi @sjnoh Please contact with Atlassian support (https://support.atlassian.com) to handle this. Support is able to fix this issue. Regards, Seba

Hi @Scott Arbery I believe that this question should be addresses on Figma's support. Regards, Seba

here you can find all details about it - https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/

Hi @Leon d_O Did you create both projects based on the same template? Regards, Seba

Hi @[deleted] Please contact with Atlassian support about that. Looks like issue on Atlassian site. Regards, Seba