-
Bug
-
Resolution: Fixed
-
Low
-
2.0.4
-
None
Steps to reproduce:
1. Try to make one of the field in JIRA as a required field (e.g. Priority)
2. Try to create the issue from the review
3. This sample message will be shown:
Error creating subtask in JIRA - Priority is required.
This is the screenshot: ErrorDisplayed
4. The problem solved when I make the field as optional in JIRA.
- is duplicated by
-
CRUC-5617 Customise which fields are set during subtask creation
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CRUC-2667] Not able to create the subtask in JIRA if some of the fields are required in the subtask creation screen
We are planning to re-vamp Issue Creation from Crucible comments in an upcoming release. Stay tuned.
Our suggested workarounds at this time are:
- Set a default value for the required fields, or
- Create a separate issue type, eg "Crucible Subtask" that has a workflow that suits Crucible (e.g. Open -> Close with no required fields). This avoids changing existing workflows, and can be more obvious in JIRA that it has a looser workflow.
Adam Myatt
added a comment - I am seeing the issue with Jira 4.4.3 and Fisheye/Crucible 2.7.11.
This issue makes jira integration unusable in our company.
Adam Myatt
added a comment - I am seeing the issue with Jira 4.4.3 and Fisheye/Crucible 2.7.11.
This issue makes jira integration unusable in our company. 
Victor Velasquez
added a comment - My company not buy crucible if this issue is not solved, ve have unlimited licence of Jira a we like to use crucible and fisheye.
Victor Velasquez
added a comment - My company not buy crucible if this issue is not solved, ve have unlimited licence of Jira a we like to use crucible and fisheye. 
Anh Dao
added a comment - We have the same issue, could not create subtask when a field is configured to be a required field. When can it be fixed?
Anh Dao
added a comment - We have the same issue, could not create subtask when a field is configured to be a required field. When can it be fixed? 
Sven Peetz
added a comment - We do have the same issue here, components is marked required for some issue-screens but not for the sub-task-screens. Creating the sub-task is impossible because components is still evaluted as a required field. Any solutions?
Sven Peetz
added a comment - We do have the same issue here, components is marked required for some issue-screens but not for the sub-task-screens. Creating the sub-task is impossible because components is still evaluted as a required field. Any solutions? 
marlene cote
added a comment - It makes it unusable here too. I am surprised that the product team isn't more responsive about this.
We won't be purchasing crucible due to this limitation.
marlene cote
added a comment - It makes it unusable here too. I am surprised that the product team isn't more responsive about this.
We won't be purchasing crucible due to this limitation. 
Michal Stochmialek
added a comment - This issue makes jira integration unusable in our company. 
We are currently trialling the new implementation, and want to ensure we have a solid solution before shipping.
Unfortunately, we can not give you a release date, however we are hoping to have something for you by the end of 2012 or very early 2013.