Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Trigger Jira workflow transition from GitHub - do not trigger "Pull request created" if pull request

Dear everyone,

Do you know whether and how it is possible to create a Pull Request Draft in GitHub - and that this creation does not trigger "Pull Request Created" in the Jira workflow transition?
This trigger shall only be performed if the Pull Request is finally created, i.e., not any longer in draft.

How can that be set up in our global Jira instance or GitHub?

Kind regards, Tilman

1 answer

0 votes
Craig Nodwell
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 18, 2023

Hi @Tilman Ulshoefer you could simply leave off the JiraID from the PR until you are ready, then add the JiraID to the PR name.  The cool thing about Jira/GitHub integration with PR's is that it will recognize edits and reflect that down into Jira.

Thank you for your answer, Craig.

We want to keep GitHub and Jira connected right from the start, so that we see in Jira which GitHub Branch/PR is connected.

Therefore, your proposal unfortunately would not help us.

In this thread, the same is asked for. Seems to be at least partially solved for Jira Cloud. 

Suggest an answer

Log in or Sign up to answer