Use a template for test days tickets #887

New issue

Open

opened 2026-03-23 14:31:32 +00:00 by kparal · 4 comments

kparal commented

2026-03-23 14:31:32 +00:00

Owner

Here's Forgejo documentation:
https://forgejo.org/docs/next/user/issue-pull-request-templates/

Here are example repos that already use templates:
https://forge.fedoraproject.org/forge/forge/issues/new/choose
https://forge.fedoraproject.org/infra/tickets/issues/new/choose

Notice that they even have contact links in there for Matrix etc, very handy!

The template can also be directly linked from pages like this one (that one might even be dropped completely and replaced by the template).

When creating the test days template, we could use this opportunity to pre-populate the body text with checkboxes, that can be later used to track the current ticket state. Instead of reading all the comments, one could have a quick look at the description and see if something needs doing for that test day. For example, we could have something like this:

Date agreed on
Wiki page skeleton prepared from a template
Wiki page finalized
Testdays app event created with an initial set of test cases
Testdays app event ready and marked as public
Calendar event created
Announcements (email, discussion, magazine, etc) prepared/scheduled
Announcements sent
Test results exported (a week after the event is over)

Thoughts?

Forgejo supports ticket templates. If we create a test days template, it will help users when asking for new test days, because we'll make sure that they don't forget to provide important details. It will also help us, it will spare us from asking many questions and we can also automatically apply labels to the ticket. Here's Forgejo documentation: https://forgejo.org/docs/next/user/issue-pull-request-templates/ Here are example repos that already use templates: https://forge.fedoraproject.org/forge/forge/issues/new/choose https://forge.fedoraproject.org/infra/tickets/issues/new/choose Notice that they even have contact links in there for Matrix etc, very handy! The template can also be directly linked from pages like [this one](https://fedoraproject.org/wiki/QA/Test_Days/Create) (that one might even be dropped completely and replaced by the template). When creating the test days template, we could use this opportunity to pre-populate the body text with [checkboxes](https://www.markdownguide.org/extended-syntax/#task-lists), that can be later used to track the current ticket state. Instead of reading all the comments, one could have a quick look at the description and see if something needs doing for that test day. For example, we could have something like this: - [ ] Date agreed on - [ ] Wiki page skeleton prepared from a template - [ ] Wiki page finalized - [ ] Testdays app event created with an initial set of test cases - [ ] Testdays app event ready and marked as public - [ ] Calendar event created - [ ] Announcements (email, discussion, magazine, etc) prepared/scheduled - [ ] Announcements sent - [ ] Test results exported (a week after the event is over) Thoughts?

kparal added the

points

Priority

Medium

labels

2026-03-23 14:32:09 +00:00

lruzicka commented

2026-03-23 15:18:58 +00:00

Owner

LGTM

jgroman commented

2026-03-23 15:29:51 +00:00

Owner

This looks really useful!
+1 from me.

This looks really useful! **+1** from me.

psklenar commented

2026-03-23 15:40:42 +00:00

Owner

LGTM.
It would be great if the checked action was reflected in Jira during the sync - at least as a comment on the ticket.

The best would be ?subtasks? with specific story points to monitor exactly what was delivered during the sprint

LGTM. It would be great if the checked action was reflected in Jira during the sync - at least as a comment on the ticket. The best would be ?subtasks? with specific story points to monitor exactly what was delivered during the sprint

kparal commented

2026-03-23 15:52:20 +00:00

Author

Owner

LGTM. It would be great if the checked action was reflected in Jira during the sync - at least as a comment on the ticket.

That's unlikely to happen. Even basic board status syncing is still broken/unimplemented.

The best would be ?subtasks? with specific story points to monitor exactly what was delivered during the sprint

I'm in contact with Rodney and Brendan about this. I've written long essays why I think it's a bad idea to do that a) in an upstream repo and b) for test days tickets specifically. I've also proposed some ways forward. We can discuss this separately. This template+checkboxes is useful in each case, I think, and was actually an idea that originated from that discussion.

> LGTM. It would be great if the checked action was reflected in Jira during the sync - at least as a comment on the ticket. That's unlikely to happen. Even basic board status syncing is still broken/unimplemented. > The best would be ?subtasks? with specific story points to monitor exactly what was delivered during the sprint I'm in contact with Rodney and Brendan about this. I've written long essays why I think it's a bad idea to do that a) in an upstream repo and b) for test days tickets specifically. I've also proposed some ways forward. We can discuss this separately. This template+checkboxes is useful in each case, I think, and was actually an idea that originated from that discussion.

kparal referenced this issue

2026-06-24 13:59:14 +00:00

Podman 6.0.0 Test Days #894

kparal added this to the Nominated next tasks project

2026-07-08 12:56:19 +00:00