Jehan Bhathena Community Champion

Hi @Phil Bustin , Please can you share a screenshot of the behavior you mention in the main question?

Hi @Avrohom Yisroel Silver , Please mark one of the Answers as Accepted, there isn't an option to delete a Community question :-P I would suggest marking your own answer as Accepted if this solved your main question.

Sorry, no clue about Java Automation.

Hi @Ankit Rastogi , Below is the way that I use response from the "Send web request" action in the Jira Automation. 1. Send Web request 2. Create variable, and in the Value, call the {{webhookResponse}} smart Value 3. Use the above variable in other actions in the SAME automation…

Hi @Ankit Rastogi , I have an automation that uses a Graphql API : Is this what you're looking for?

Just to be sure, Is your automation setup to trigger when "Approval Completed" ? Or is it using the "Issue transitioned" trigger. If it is the latter, try changing it to "Approval Completed" and then check if the Approval name is logged.

Hi @Raghu Mani , (wasn't able to solve this, but adding my 2 Cents to the conversation) The description in Jira is formatted with DOC type i.e. "type": "doc" (as per the API response), so it wont preserve the formatting when sending the data ahead using the {{issue.description}}. In theory, perhaps you can attach the…

Got it. Just as a side note, if @Valerie Knapp 's answer helped out in solving the issue, please mark this thread as "Accepted", that way it becomes more visible to other users looking to solve the same issue.

Hi @Ste404 , Would you be able to share the workflow (with the approval steps highlighted), and the Automation as well? Perhaps I can try to replicate the setup at my end to check this. :-)

Hi @Ste404 , By Blank value, do you mean nothing was printed out when the automation was triggered? 

Hi @靳光光 , Did {{issue.resolutiondate}} work for you?

Hi @Mguiss_ Anis _AllianzGI_ , Offline test exporter is actually a template in the document exporter. Document generator can also be customized to have the desired formats, perhaps that might be of help? "Test Steps" Are a x-ray specific field, so it won't be visible in the regular Jira Filter view. You might need to raise…

Hi @Büşra Öztürk , You can try this method: * Add User to the site, uncheck the invite and without access to any product * Now add the user to the Jira-software group that grants Product Access Let me know if this work 🙂 PS: If this works, you can use Postman to bulk add a set of users to the required group.

Hi @JIM_PROVO , I'll second @John Funk 's answer, a status name is something that you can define for your self. In our use case we use "Ready" When the ticket is analyzed and good to go under development, where as "Ready to Ship" Is more of a deployment status which we use to identify tickets whose work is completed and…

@Ste404's point is quite valid, there is a very weird behavior here. in the below image you can see the Excluded Approver filled, I tried to keep it empty but that too didn't work. To get this to work at my end, I had to empty all the "Exclude Approvers from" -> "Publish Workflow" -> Return to the Ticket. For the change to…

Hi @Giulia Quaglia , from your above comment it looks like you're passing the complete field value, if this is a User related field you'll need to make thr output more specific, taking reference from @Bill Sheboy 's answer try using this as the comment (Square bracket is for tagging)…

Hi @Nithin VS , I would recommend creating a screen that uses rhe resolution field. Now use this screen in your workflow when transitioning from In-Progress to Done. This will help you "Resolve" Your issue when marking it as DONE. Another check I recommend is clearing the resolution when the ticket gets reopened. Hope this…

Hi @Mguiss_ Anis _AllianzGI_ , X-Ray has an in-built document exporter, that allows us to export test cases with the steps. Try using the "Offline Test Exporter" And see if that fulfills your use case.

Hi @riccardo.pedrinelli , If both the issue types belong to the same project then perhaps clubbing them under the same Workflow, Screen Scheme and Field Configurations would help. Same would apply they falls under 2 different company-manged projects.

You'll just need to un-check the below option when inviting the user :

Hi @Ste404 , The below automation should help : It gets triggered when the ticket is approved and the approver name can be used with this smart value : {{approval.approver.displayName}}

Hi @Büşra Öztürk , Do you mean the notification that Admins receive when a user is added or requested to be on-boarded? Or do you mean the User Invites that are sent when adding a User into Jira/Confluence.

Hi @Beraud romain , Great to know you found the solution. Please can you share what setup you did to achieve this, I was try to add 2 forms to the same request type, but didn't work at my end. (I can add another form via the Agent View, but that isn't my end goal)

Hi @Rajesh K , Based on your query "filtering open to rejected bugs with assignee as a particular group" You can try : status changed FROM Open TO Rejected AND assignee in membersOf("Groupname") Or if you want to include the 2 Statuses , then : status in (Open,Rejected) AND assignee in membersOf("Groupname") Reference : *…

Hi @Karin van Driel , I understand your frustration, and totally agree that the support portal isn't always optimal for Critical or showstoppers it is one of the best ways to communicate with Atlassian. Being a Enterprise customer, you should be assigned a Customer Success Manager from Atlassian's team itself, and they can…

Great catch 🙂 Thanks for sharing your solution.

Hi @James Ramsden , I think your request is better redirected to the Support team https://support.atlassian.com/.

By global custom fields do you mean fields like "Epic Links", Time Estimates etc. I didn't find any read ups on these fields unfortunately.

Hi @Lindsey Abrahamsen , Few posts that might be relevant (not a concrete answer) : * https://community.atlassian.com/t5/Jira-Software-questions/Feature-issue-type-between-Epic-and-Story/qaq-p/1707157#M142287 *…

Hi @Leena Pratheepan , As the audit log mentions, try to un-check "Only include issues that have changed since the last time this rule executed", and wait for the Rule to run again. Please let us know if that works.