Transitioning issues in JIRA

Transition a JIRA Software issue from within FishEye in any of the following ways:

Transition an issue automatically

Your JIRA Software workflow can now respond to events in your linked development tools. For example, when a commit is pushed, your JIRA Software workflow can be configured to automatically transition the related issue. Configure this using triggers for transitions within the JIRA Software workflow editor.

The events published by FishEye are:

  • Commit created
  • Branch created

A FishEye administrator can disable event publishing if required. See JIRA workflow triggers.

FISHEYE 3.5.2+ JIRA 6.3.3+

Transition an issue manually from FishEye

FISHEYE 3.1+

You can easily transition a JIRA Software issue from within FishEye. For example, when viewing a commit, you may want to transition the related JIRA Software issue to the QA status. Click on a linked JIRA Software issue key in FishEye to see a dialog with the available workflow steps:

Click on a step in the dialog, and complete any displayed fields as required. If there are custom required fields that are unsupported by FishEye, just click Edit this field in JIRA Software to go to JIRA Software to transition the issue.

Transition an issue with your commit message

FISHEYE 2.7+

Use Smart Commits when you are committing to a repository hosted in FishEye to transition JIRA Software issues. Smart commits allow you to embed commands into your commit messages, which FishEye detects and actions.

For example, if you include the following text in your commit message, FishEye will add the comment 'Task completed ahead of schedule' and resolve the issue, when you perform your commit: 

JRA-123 #comment Task completed ahead of schedule 
#resolve

Read more about Using Smart Commits.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport