-
Notifications
You must be signed in to change notification settings - Fork 131
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
Include more fields in Create Issue modal #583
Conversation
The client go-jira client library used doesn't implement label search. This means changes had to be made to the GetClient method on Jira Instance interface to also return http.Client that is configured and sent to NewClient method of the go-jira library. Delete console.log statement Clean up code Remove unused go package and update webapp snaps Use RESTGet in GetLabels Remove unnecessary function arg, url Make autocomplete search more generic Fix a comparison error Make front end autocomplete components generic
Codecov Report
@@ Coverage Diff @@
## master #583 +/- ##
==========================================
- Coverage 34.50% 34.00% -0.50%
==========================================
Files 51 52 +1
Lines 5684 5766 +82
==========================================
Hits 1961 1961
- Misses 3530 3612 +82
Partials 193 193
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small change proposals.
webapp/src/components/data_selectors/jira_autocomplete_selector/jira_autocomplete_selector.tsx
Outdated
Show resolved
Hide resolved
- handle case where changing issue type or project causes invalid fields to be filled out - handle clearing a single select value properly
@jfrerich This is ready for review |
Most of the diff is due to snapshots that contain the Jira issue metadata as a prop passing to several children. Looking at the jest testing docs and forums, it doesn't seem like this is avoidable unless we get rid of the snapshot tests. |
@mickmister issue 2B. occurs on Cloud only. I can create a separate issue for this. It was not introduced by this PR. I see it on Jira v3.0.0 Version bump branch. |
@DHaussermann Do you know which bugs that were introduced in this PR that must be addressed here? |
@mickmister I've taken another look at the issues here:
Reach out if you'd like to discuss this. |
/update-branch |
Error trying to update the PR. |
Codecov Report
@@ Coverage Diff @@
## master #583 +/- ##
==========================================
- Coverage 32.38% 31.92% -0.46%
==========================================
Files 52 53 +1
Lines 5361 5437 +76
==========================================
Hits 1736 1736
- Misses 3423 3499 +76
Partials 202 202
Continue to review full report at Codecov.
|
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
@DHaussermann I think I need to use your Jira setup to reproduce 2a. and 2c. |
Reviewed this PR with @mickmister
|
Codecov Report
@@ Coverage Diff @@
## master #583 +/- ##
==========================================
- Coverage 35.16% 34.70% -0.46%
==========================================
Files 51 52 +1
Lines 5827 5909 +82
==========================================
+ Hits 2049 2051 +2
- Misses 3573 3653 +80
Partials 205 205
Continue to review full report at Codecov.
|
/update-branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and passed
- Working on Cloud and server instances as per previous testing
- Epic Link is now functional on both Cloud and server
- Failing snapshots are now esoved
- Created Data missing from Jira issue when unsupported custom fields are mandatory #794 to address the remaining issue in a separate PR
LGTM! please merge
Summary
You can now use every applicable Jira field in the Create Issue modal. Basically all of them except date pickers.
Ticket Link
Fixes #563
Fixes #520
Fixes #394
Fixes #471
Fixes #502