Crucible: How to create inline issue with Assignee field

[Pirax]

Hi,

I am using selfhosted version of JIRA 5.2 integrated with Crucible 3.0 - both recently updated.

What I want to achive is to create inline issue from Crucible and have the possibility to select/type issue assignee, which I had in previous version. To be honest there are more fields I would like to see during inline creation, but I dont want them to be mandatory.

And my main problem is how to achieve that?? Ive read that if I want specific field to appear in crucible's inline create issue screen I need to make the field "required" in JIRA (I dont want to do it anyway, but that's not the point), but according to documentation/forum/my panel Assignee field cant be made "required"... (??).

Two questions then:

1. How can I display Assignee field in inline issue creation screen in Crucible?

2. How can I display a field in inline issue creation screen in Crucible without making it mandatory?

Thank you for your help.

[Pirax]

Hi Geoff,

Thank you for you answers.

1. OK, i will wait then.

2. Customisation will be the best solution to be honest - using "required" option is really uncomfortable and not usefull - I am not really sure how others use JIRA/Crucible integration but we use it to its core and inline issues creation is one of the most commonly used operations. It makes our job ineffective - firstly we need to create "crippled" issue from Crucible and secondly - edit it to our needs in JIRA.

And to answer your question:

Old sub-task creation allowed reviewers as assignee - or at least it looked like this ;) It was not ideal sollution but alowed us - with small dose of magic - to achieve what we wanted.

Thanks,

Przemek

[Geoff Crain]

Hi Przemyslaw,

When we implemented the new inline issue creation we wanted to keep it as simple as possible, with scope to improve it based on specific customer feedback - so thanks for your questions!

1. The Assignee field currently isnt supported as the field always has a default (either Unassigned or the specified default assignee), and its more complex to do properly than we wanted with an initial implementation. https://jira.atlassian.com/browse/CRUC-6545

2. Crucible currently only shows required fields + the description field. This was to make it as quick / light weight as possible. We can certainly look at adding other fields if they exist on the issue (like Assignee), or making it customisable. https://jira.atlassian.com/browse/CRUC-6544

A question for you:

The old sub-task creation allowed "Unassigned", <You> and <Assignee of parent issue> (I believe). Would this be acceptable to you, or would you need arbitrary assignees?

Cheers,

Geoff

[Xiang(Leon) Zhang]

Hi Geoff as a follow up to this question has any head way been made here? We have a drop down in JIRA called scrum team we'd like to see on issue creation in Crucible. We tested last night by making it a mandatory field hoping it would show up in Crucible but it did not.

[Geoff Crain]

Hi Xiang,

Unfortunately we haven't implemented it yet, though it is definitely still in our sights, as with better integration with JIRA in general.

We've built some improved field support into Stash, and we're standardising some internal libraries so that Crucible will get these improvements soon, too, though we can't give out specific dates.

If you have a specific request for custom field types, please raise a feature request, or you can add a comment to https://jira.atlassian.com/browse/CRUC-6545and we can look at working on it at the same time.

Cheers,

Geoff