Why do I encounter two different types of inline sub-task issue creation. One that
(1) does not work for me and has error "We couldn't create the subtask".
(2) works fine as there is a popup window to allow proper input
How do I configure my project to use only option (2) method?
Hi @David Gan and welcome to the community,
For better understanding: Could you please specify your requirement in more details?
Best
Stefan
Thank you Stefan!
For example, this is how normally test scenario sub-tasks are created in my environment.
Once I typed in the Summary and click Create this popup Window appears and I can input the rest of the information and save.
But I have created another set of schemes with new sub-tasks which resulted in
But this time the detail input popup window does not appear and the Jira is unable to create the sub-task with below error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @David Gan ,
Could you please show the whole issue?
Are those screenshot from the same issue within the same project? Which issue-types are the main/standard issues you want to create sub-tasks to?
Are there any screen schemes or required field associated? Or any validator in the workflow for the create transaction?
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Stefan Salzl ,
Here is how the whole issue looks like. I have created an entirely new set of screen, workflow and issue type schemes and adopted the Light Weight Test Case Manager workflow from marketplace. I then associate these to a new project.
The Test Scenario is a sub-task that I should be creating under Story. There is no validator that I am aware of.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As there have been many different changes at once all of these things needs to be considered to recheck with your configuration before those changes.
Best
Stefan
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.
Hi @David Gan
If your problem could be resolved please consider to click the Accept button in order to have this question marked as "Solved".
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have finally found the cause of the issue. It is due to create issue permission not given. But the Jira error could have been clearer.
Anyway much thanks for your assistance. Appreciate it.
Best regards,
David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.