-
Notifications
You must be signed in to change notification settings - Fork 6
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
Validate and add configurability for Jira issue link types; bug fixes #33
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #33 +/- ##
==========================================
+ Coverage 95.01% 95.17% +0.15%
==========================================
Files 1 1
Lines 281 290 +9
==========================================
+ Hits 267 276 +9
Misses 14 14
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Thanks a lot. It looks good. Let's test it in real like with Bert. |
@JasperCraeghs : I reviewed and tested it. It is OK according to me. I can not approve, so will you ask @Ben2022 to approve or do you make me the approver? |
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.
Approved by Bert
Blocks
, configured by Atlassian for Jira Cloud.[-L [LINKS ...]]
to override the default configuration of Jira issue link types to take into account for TaskJuggler'sdepends
keywordKeyError
inif not id_to_task_map[identifier].is_resolved:
depends
, resulting in an error by TaskJuggler:Error in scenario plan: No need to specify dependency X multiple times for task Y.
Closes #32