Add support for new parent field as an alternative to linking

[tj-smith47]

Please consider opening a discussion in ideas category if applicable. Your feature will be prioritized on based on the number of votes.

Is your feature request related to a problem? Please describe.
I use this tool heavily in my daily workflow. I've just recently been informed some teams would rather we link tickets to epics through the new Parent field rather than linking it as blocked. I believe this may be possible with the --custom flag, but I can't find any examples of that being used.

Describe the solution you'd like
Add a --parent flag to jira issue edit

Describe alternatives you've considered
I believe this may be possible with the --custom flag, but I can't find any examples of that being used.

Additional context
This project is absolutely amazing - thank you for all of the hard work you've done to manifest and support this tool!

[tj-smith47]

Update:

I'd like to append to this request the ability to view the parent linkage in jira issue view. I currently have a workflow that runs against a board and audits that everything is sorted into the correct swim lanes. One of the triggers preventing this from working fully as it could is that if a ticket doesn't have a parent linked, it would get sorted to column A, and if it does to column B. For my use case in particular, I would only need a binary "has parent" / "doesn't have parent" level of detail, but the most sensible I think would be in the first line of the banner for jira issue view --plain that would show something to the effect of 👪 BRD-12345 (not really a great emoji for parent, but you get the idea).

It looks like the parent field is accessible in the V2 Get Issue endpoint via:
curl -H <headers> -u <user:pass> <base_url>/rest/api/2/issue/<issue_id> | jq -r '.fields.parent.key'

The documentation only mentions "Parent" through .fields.["sub-tasks"] | select(.type.inward == "parent"), though that field is empty on tickets I've tried with parents.

[ankitpokhrel]

Hi @tj-smith47, first part should be fixed with #765. I created another issue for second part, will hopefully add it soon. Thanks for reporting!

[tj-smith47]

Awesome! Thank you as well for all of your hard work 🙏🏼 if not for this project, I may never have gone down the rabbit hole of realizing just how powerful a language Go is for creating awesome CLI tools.