Axon 726 be able to assign epic parent in create issue webview #651
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…need filtering functionality.
Migelangel04
requested review from
bwieger-atlassian-com,
sdzh-atlassian,
cabella-dot,
marcomura,
akalia-atlassian and
pastelsky
as code owners
…eate-issue-webview Merge branch with main
…Picker that is more pleasant for the user. Still waiting to see if we can get some Server functionality and will come back to this if time permits to create a Server funcitonality. Otherwise, this branch feature gates it for Cloud users in the seperate tsx pages minus the UI updates to the select issue (which is also used in the issue links.
…eate-issue-webview Merge with main
…r only has one parent-child relation) Restored functionality to Serevr for subtasks. Epics to Standard Issues do not have standard parent and child relationships because DC has a different term/schema for epic and epic children. Epic children refer to their epics as 'Epic Link' rather than 'Parent' as subtasks refer to standard issues in Jira. This means that this task is done if we are going all issues that we can assign to as parents. To have standard issues connect to Epics, we would need to expand the task to include all parent-child as well as epic-epic children. Also with our current apis, a standard issue in Jira DC has no way to know if it has any connected epic links because it does not show under fields or field values.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What Is This Change?
Being able to give an issue a parent on creation of the issue and within the editor as a field. Cloud has a general parent and child relationship so established functionality for all issue types with the top parent being epics. Server instances of Jira only support one type of child and parent issue relationship (Sub-task to standardIssueType()). So far Cloud is fully supported and working out the last kinks for Server. StandardIssues to Epics are not a standard parent-child relationship as they refer to an Epic via the Epic Link field (not the parent field) and Epics refer to standard issues as "Epic Children" (weird I know).
How Has This Been Tested?
Basic checks:
npm run lintnpm run testAdvanced checks:
Recommendations: