action #129871
closed[tools] [openQA] Optically split build in group and search fields.
0%
Description
openQA web shows in group view and in search results BUILD as BuildBUILD which is confusing because real BUILD is suffix after word Build. So we should split this to lower confusion or remove Build prefix.
Unfortunately we allow empty BUILD BUILD='' schedules job with empty build and if we remove prefix we will lost link to job/build
proposed solution: https://github.com/os-autoinst/openQA/pull/5144
Updated by osukup over 1 year ago
- Subject changed from Optically split build in group and search fields. to [tools] [openQA] Optically split build in group and search fields.
Updated by okurz over 1 year ago
- Category set to Feature requests
- Target version set to Ready
Users will have got accustomed to the missing separator, think about the actual build values for SLE maintenance. So at least we should give users some means to control it I guess
Updated by osukup over 1 year ago
okurz wrote:
Users will have got accustomed to the missing separator, think about the actual build values for SLE maintenance. So at least we should give users some means to control it I guess
I think best will be to validate* BUILD and forbid using empty string as value and then remove prefix completely
- and apply same rules as for tag parsing in comments -- so we can be sure any BUILD can be tagged
Updated by okurz over 1 year ago
I still don't understand if you only see a cosmetic issue or is a functional problem in certain cases?
Updated by okurz over 1 year ago
- Status changed from New to Rejected
- Assignee set to okurz
Within the weekly estimation meeting of SUSE QE Tools 2023-06-22 discussing benefits and drawbacks of different solutions and different possibilities, e.g. leaving out the prefix "Build" or adding an explicit separator like ":" or " " or "-". In the end we decided that it's most consistent if we keep everything as is. Reasons:
- Users are used to that since more than I guess 10 years now.
- In the job scenario we consistently use "-" to separate different categories for naming so we should not use "-" to separate within the category "build" the prefix "Build" and the value
- Due to version-prefixes in displayed build strings when the build value is used multiple times for different versions we have strings like "12-SP3-Build42.1". Splitting that with " " would be confusing as it would split the complete version-build string within the build field