-
-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to set parent field #738
Comments
I'm seeing a similar problem. Except when I try and set the parent I end up with an error
|
Maybe @ankitpokhrel has any lead |
@electriquo @SleepyBrett |
@jcstorino Although I tried, I couldn't understand what did you mean. Could you please share a concrete example? |
Sure...
Open this file and look for the project key, below must exist another key with name "type", change its value to "next-gen" and test again the creation of an issue with the --parent option. It worked for me.
|
@jcstorino Thanks. Change from project:
key: TDC
type: classic to project:
key: TDC
type: next-gen Will try it later on this week and let your know. |
Describe the bug
Creating an issue with parent field or parameter does not work.
Browsing the issue in the browser, I see that it does not have the parent field. So I tried to analyze the fields of the created issue using the API and as you can see, the parent field was not set.
I repeat the analysis on an issue with the parent field set correctly
Clearly, that in the browser I did not set all these values for the parent field. The parent field is a select box to pin an issue that is the parent (some call this an epic), such as selecting ISSUE-12345 (see the screenshot below).
Then I tried to look for the custom field in the CLI configuration
So I tried setting this custom field by editing the issue, but got an error
Both the parent and the parent-link fields does not apply for the ticket even when the
--parent
option was used.How can I set the parent field to value such as ISSUE-12345 using the CLI?
How do I find the parent field type (maybe it has to do something with the configuration, see Caveats at the Additional context below)
Please provide following details
To Reproduce
See description.
Expected behavior
The parent field to be set and once set, it must be listed in
jira epic list <parent issue number>
.Screenshots
This how the parent field look in the browser
Additional context
The text was updated successfully, but these errors were encountered: