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
Auto-mapping is library feature, that is enabled by default and is converting every issue field name into it's human form, e.g.
summary becomes Summary
issuelinks becomes Linked Issues
Unfortunately it only works for issue itself and not linked issues.
For example if I specify summary,status,issuelinks as $fields parameter of Walker class (instead of *navigable) I'll get Linked Issues field with this content:
In there the inwardIssue and outwardIssue keys represent the linked issue. Note, that even with automapping enabled I see summary key name instead of Summary and so on.
The text was updated successfully, but these errors were encountered:
Auto-mapping is library feature, that is enabled by default and is converting every issue field name into it's human form, e.g.
summary
becomesSummary
issuelinks
becomesLinked Issues
Unfortunately it only works for issue itself and not linked issues.
For example if I specify
summary,status,issuelinks
as$fields
parameter ofWalker
class (instead of*navigable
) I'll getLinked Issues
field with this content:In there the
inwardIssue
andoutwardIssue
keys represent the linked issue. Note, that even with automapping enabled I seesummary
key name instead ofSummary
and so on.The text was updated successfully, but these errors were encountered: