Project

General

Profile

Actions

action #137837

closed

[spike solution][timeboxed:10h] Come up with a ticket template extension that strongly encourages reproducers and impact be included size:S

Added by tinita about 1 year ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2023-10-12
Due date:
2024-02-21
% Done:

0%

Estimated time:

Description

Motivation

See #136007

Acceptance crtiteria

  • AC1: We know if we can use the RedMine plugin and if it is good enough for us

Suggestions

  • As necessary make a followup ticket for automated comments with instructions on new tickets not following the ticket template structure, then extend our due-date automation or another script to comment on tickets not following the ticket template, suggest to use the "report issue" button from openQA
  • Research if we can provide templates via a RedMine plugin https://www.redmine.org/plugins/redmine_issue_templates

Related issues 4 (3 open1 closed)

Related to openQA Project (public) - action #154063: [tools] Provide a template for tickets that includes commonly required detailsNew2024-01-19

Actions
Copied from openQA Infrastructure (public) - action #136007: Conduct "lessons learned" with Five Why analysis for network protocols failures on multimachine tests on HA/SAP size:SResolvedtinita

Actions
Copied to openQA Project (public) - action #155086: Install and enable Redmine Issue Templates on ProgressNew2023-10-12

Actions
Copied to openQA Infrastructure (public) - action #155089: Automatically comment on tickets not using one of our templatesNew

Actions
Actions #1

Updated by tinita about 1 year ago

  • Copied from action #136007: Conduct "lessons learned" with Five Why analysis for network protocols failures on multimachine tests on HA/SAP size:S added
Actions #2

Updated by okurz about 1 year ago

  • Target version set to Tools - Next
Actions #3

Updated by okurz about 1 year ago

  • Tags deleted (infra)
Actions #4

Updated by tinita about 1 year ago

  • Subject changed from Come up with a ticket template extension that strongly encourages reproducers and Impact be included to [spike solution][timeboxed:10h] Come up with a ticket template extension that strongly encourages reproducers and impact be included size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions #5

Updated by okurz 11 months ago

  • Target version changed from Tools - Next to Ready
Actions #6

Updated by okurz 11 months ago

  • Related to action #154063: [tools] Provide a template for tickets that includes commonly required details added
Actions #7

Updated by livdywan 10 months ago

  • Status changed from Workable to In Progress
  • Assignee set to livdywan

I'm taking a look at this

Actions #8

Updated by openqa_review 10 months ago

  • Due date set to 2024-02-21

Setting due date based on mean cycle time of SUSE QE Tools

Actions #9

Updated by livdywan 10 months ago

  • Status changed from In Progress to Feedback

https://github.com/agileware-jp/redmine_issue_templates#1-plugin-installation

Looks pretty straightforward. Code is actively being developed.
I'm not sure how risky the "migration" might be. Probably similar to tags support. We should expect it to break now and again.

For reference I also checked what alternatives we might have:

There is nothing about installing the plugin in this ticket, so I can´t say for sure if this is "good enough" for us. I would suggest as a follow-up we figure out how to get it installed. Maybe asking @crameleon for help.

Actions #10

Updated by livdywan 10 months ago

  • Copied to action #155086: Install and enable Redmine Issue Templates on Progress added
Actions #11

Updated by livdywan 10 months ago

  • Copied to action #155089: Automatically comment on tickets not using one of our templates added
Actions #12

Updated by okurz 10 months ago

livdywan wrote in #note-9:

https://github.com/agileware-jp/redmine_issue_templates#1-plugin-installation

Looks pretty straightforward. Code is actively being developed.
I'm not sure how risky the "migration" might be. Probably similar to tags support. We should expect it to break now and again.

For reference I also checked what alternatives we might have:

There is nothing about installing the plugin in this ticket, so I can´t say for sure if this is "good enough" for us. I would suggest as a follow-up we figure out how to get it installed. Maybe asking @crameleon for help.

I don't know what feedback exactly you wait for. Are you waiting for us within the team to tell you if we like the above solution? Or did you already ask @crameleon ?

Actions #13

Updated by livdywan 10 months ago

  • Status changed from Feedback to Resolved

I don't know what feedback exactly you wait for. Are you waiting for us within the team to tell you if we like the above solution? Or did you already ask @crameleon ?

I follow best practice which means giving others a chance to say that I forgot something before I resolve the ticket. If all seems fine that is totally okay.

Actions

Also available in: Atom PDF