How do I customise the change ticket created during deployment gating

[Victor Amadi]

I have some required fields in my change ticket and I need them to be filled when Automation for Jira creates the Change Ticket during the deployment gating process

[Marc - Devoteam]

Hi @Victor Amadi 

@Priyanka Khare can be right, but it would be useful to help you, if you provide:

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 for not willing to help, but to have community members understand on how automation works.

[Priyanka Khare]

Hey @Victor Amadi 

Please try the below-

Trigger: Use "Issue Created" or similar trigger for the deployment process.

Action: Select "Edit Issue" or "Create Issue" to set required fields.

• Use smart values (e.g., {{issue.summary}}, {{deployment.version}}) to auto-populate fields.

Ensure Workflow: Make sure the fields are not restricted by workflow conditions.

Test: Run a test to ensure required fields are populated automatically.

Let me know how it goes!

[Victor Amadi]

thank you so much guys, I totally forgot that I raised this question and got responses.

Apologies for my late reply, but thank you @Priyanka Khare your suggestion actually was an approach I considered, but then I found out that the values we needed to fill the ticket with came from the bitbucket pipeline, so we had to use pipes to create the ticket during the pipeline run