You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 forjira 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'
Originally posted by @tj-smith47 in #714 (comment)
The text was updated successfully, but these errors were encountered: