Summary

When creating a Crucible review starting from a Jira issue, the review Objectives field will contain different information sent by Jira depending on if the 'Create review' (for a single changeset) or 'Create review for all commits' was clicked in the Development Panel modal window and if the Jira issue contains a description.
 

Environment

• Jira 7.5.0 applinked to Fisheye/Crucible 4.5.0
• Application link fully functional using OAuth (without impersonation)

Steps to Reproduce

1. Open the Development Panel modal window:
   
2. When using the 'Create review' link for a specific changeset listed, regardless if the Jira issue contains a description or not, the changeset ID turned into a link is referenced in the Crucible review Objectives field, along with its commit message:
   
3. When using the 'Create review for all commits' option, if the Jira issue has a description, the review Objectives field will contain the Jira issue description:
   
4. When using the 'Create review for all commits' option, if the Jira issue does not have a description, the review Objectives field will contain a list of the changeset IDs turned into links, and their respective commit messages:
   

Expected Results

Jira should send consistent information to the Crucible review, when either the 'Create review' or the 'Create review for all commits' link is clicked, to be added in the Objectives field. It should either:

1. Send the issue description along with the list of commits IDs and their messages
2. Send just the issue description or just the list of commits IDs and their messages

Actual Results

Jira sends inconsistent information to the Crucible review depending on if the 'Create review' (for a single changeset) or 'Create review for all commits' was clicked and on if the issue contains a description.

Workaround

There are no known workarounds.