We are successfully using JIRA OnDemand with SVN and Crucible to create code reviews. It's all good, but ... we have never seen the Create issue/sub-task button appear in the code review comments that we generate for each other. Working carefully through the Administration pages and reading the material on the web hasn't yielded an answer. We're stumped. This is what we've done so far, but it has failed to enable the Create issue/sub-task button to appear within the code review comment widget in an active review.
Check that Subtask Resolution Action ID is not empty.
I double checked that and the JIRA issue is listed in the Details window as a linked issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are sub tasks disabled in your Jira instance by any chance?
http://confluence.atlassian.com/display/JIRA/Configuring+Sub-tasks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I read through the material and went to Administration > Issues > Issue Types > Sub-Tasks
I see:
Sub-tasks are currently turned ON. You can manage ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, next check, are you able to manually create a sub-task in Jira for that linked issue? Just to check your permissions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Permissions seem okay. This is what I did based on your suggestion:
Issues > Create Issue
Then I filled in a reasonable set of fields in the form (it's the standard form out of the box from OnDemand). Once the I'd finished creating the issue, I navigated into the issue and went:
Move Actions > Create Sub-Task
I was taken to the Sub-Task form where I created a new Technical Task. That all worked - although the only Sub-Task type I can create is a Technical Task and when I expand the drop down list of task types in the Sub-Task creation dialog, it is empty. I would expect to at least see Technical Task listed. Perhaps the fact that it is listed as my selected choice for Sub-Task type keeps it out of the drop down list.
Back in the parent task I saw the new Technical Task listed. Then, to check things out further, I created a new Review, with the new parent issue (not the sub-issue) as the linked Issue. The Review got created and I made a code comment on a file, but once again the Create issue button did not appear in the inline comment.
One thought I've had is that the "Technical Task" sub-task is incompatible with whatever logic Crucible uses to determine whether to show or not show the Create issue from inline comment.
Thanks, I appreciate the help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That reminds me, in your Crucible Jira configuration you would have specified the issue-type of the 'sub-task'. Is that issue type number matching that of the Technical Task (see the screenshot here)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am able to get to some of the steps (I've pasted them below for reference from the link you sent me) in OnDemand, but others don't appear to be available through the OnDemand administration menus. For example, steps 6 thru 8 (inclusive) are all available to me as the Administrator ... but through a slightly different path (Administration > Issues > Workflows > Workflows). That works okay.
But steps 2 thru 5 (inclusive) don't work in OnDemand -- at least I can't figure them out the OnDemand navigation. If I go to Administration > Reviews then I see three submenus:
This is odd, because I figured there would be somewhere in OnDemand where the internals of the Crucible - JIRA linkage are made visible, like they seem to be in the non-hosted version of JIRA / Crucible.
Perhaps it all comes to this gap -- the "issue type number match" that you mention
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am at loss what to check next. May be it's time to poke Atlassian via a support request.
May be a last check. This username that you are using to connect to Jira, is that account having permission on the project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is your review linked to the Jira issue in the details window?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.