Jira Workflow Automation

Discuss general development subjects that are not specific to a particular version like the versioning control system we use or other infrastructure.
Post Reply
User avatar
naderman
Product Manager
Product Manager
Posts: 1727
Joined: Sun Jan 11, 2004 2:11 am
Location: Karlsruhe, Germany
Contact:

Jira Workflow Automation

Post by naderman » Thu May 28, 2015 1:22 pm

I've started to set up Jira Workflow Automation, and will post in here as I make more progress.

For now the state of an issue is automatically moved to "Patch awaiting review" if you create a Pull Request mentioning the respective ticket id.

User avatar
naderman
Product Manager
Product Manager
Posts: 1727
Joined: Sun Jan 11, 2004 2:11 am
Location: Karlsruhe, Germany
Contact:

Re: Jira Workflow Automation

Post by naderman » Thu May 28, 2015 1:28 pm

Further, when you merge a pull request the ticket is automatically marked as merged. If a pull request is closed without being merged the issue is reset to Open.

User avatar
naderman
Product Manager
Product Manager
Posts: 1727
Joined: Sun Jan 11, 2004 2:11 am
Location: Karlsruhe, Germany
Contact:

Re: Jira Workflow Automation

Post by naderman » Fri May 29, 2015 9:55 am

When you create a new Pull request now without mentioning a ticket id in the pull request a new issue will automatically be created. The link to it will be appended to the pull request description.

User avatar
nickvergessen
Former Team Member
Posts: 733
Joined: Sun Oct 07, 2007 11:54 am
Location: Stuttgart, Germany
Contact:

Re: Jira Workflow Automation

Post by nickvergessen » Sun Jun 21, 2015 3:05 pm

We need a fix for this:
when someone sends a master based PR against 3.1 and we close the PR, JIRA will reopen all 3.2 issues that have been merged :-O
Member of the Development-TeamNo Support via PM

Post Reply