Project

General

Profile

action #88564

coordination #58184: [saga][epic][use case] full version control awareness within openQA, e.g. user forks and branches, fully versioned test schedules and configuration settings

coordination #88561: [epic] Extend needle version control handling

text field for git commit details in needle editor

Added by okurz 5 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2021-02-12
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

See Use case 4
and came up as idea during the SUSE QE Tools workshop 2021-02-12: When saving needles from the webUI we already store "who", "when", "what" but the "why" can only be encoded into the filename. As we store every needle in git we could benefit from an optional text field to fill into git commit details

Acceptance criteria

  • AC1: The body of automatically generated git commits can be filled from text that the user enters over the webUI needle editor
  • AC2: Users can still save needles without needing to fill the optional details

Suggestions

  • Research how we already save the current user name into git and how we read out the optional reason field in the needle editor
  • Add a test!
  • Add a text field over the webUI needle editor to take an optional git commit message body (or subject overriding the current auto-generated?)
  • If text in optional text field then save that in the git commit message

History

#1 Updated by mkittler 5 months ago

  • Assignee set to mkittler

#2 Updated by openqa_review 5 months ago

  • Due date set to 2021-03-05

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

#4 Updated by mkittler 5 months ago

  • Status changed from Workable to In Progress

#5 Updated by mkittler 5 months ago

  • Status changed from In Progress to Feedback

Only waiting for codecov to merge the PR.

#6 Updated by mkittler 5 months ago

  • Status changed from Feedback to Resolved

The PR has been merged. Having it tested locally should be sufficient, I'm not going to create a test commit in the production repository. (We can always reopen the ticket if it doesn't work in production.)

#7 Updated by okurz 5 months ago

That's ok. However, this ticket could be another feature that we might want to provide some marketing about. So, could you maybe present that in a SUSE QE Tools workshop or a blog post or mailing list post or video (or feature tour addition)?

#8 Updated by okurz 5 months ago

  • Due date deleted (2021-03-05)

Also available in: Atom PDF