-
Notifications
You must be signed in to change notification settings - Fork 5
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
Modify Jira pipeline adding new issue types #49
base: master
Are you sure you want to change the base?
Conversation
@@ -15,6 +15,6 @@ jobs: | |||
- name: Set up Python environment | |||
uses: actions/setup-python@v1 | |||
with: | |||
python-version: "3.8" | |||
python-version: "3.10.16" |
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.
Needed so that flake8 works
@@ -45,6 +37,15 @@ def filters(self): | |||
|
|||
return self.client.get_search(query) | |||
|
|||
def filters_new_issue_type(self): |
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.
I am using a new filter to not to mess up with the info we have from Requests up until now. Starting this year, even though we still have Requests, there are Internal Tasks and Sub-Tasks, and for those, now we rely on labels to filter and group them. Requests from last year or earlier do not all have labels and filtering them has been difficult when using the new query.
# JQL query All QA Needed iOS filter_id: 13789 | ||
FILTER_ID_QA_NEEDED_iOS = "13789" | ||
|
||
# JQL Extra fields needed | ||
JQL_QUERY = 'jql=filter=' |
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.
Moving here all these constant values
Before this lands I have to create the new table: |
Adding support for the new IssueTypes. With these changes the new table is populated with the required data.
Graphs need to be updated pointing to the new table.
I would need to think of a transition plan so that data is not lost.