Hi Wes and Sebastian,
thank you both for your suggestions!
I managed to decrease the number of the proposed key words - I excluded those that overlap with the "Component" and "Label" fields, and those that are too specific. Instead, I left only those that pertain to specific screens or features that will make it easier to distinguish the test cases from each other. I think the categories can't be broader, as those under the "Component" and "Label" fields are broad, and they don't render searching for the test cases fast enough - they are not specific enough and there are too few of them. Though of course I think we should still keep using them, along with the new custom field. I think the latter should be called "Keyword", and it should be a drop-down list from which one could select suitable options, as Sebastian suggested, so that we don't create countless options, as is the case as far as the "Label" field is concerned.
As for the "Automated", "CT" and "FT" keywords, I thought that we should label the tickets with manual test cases with these labels/keywords, so that we know what features that had been previously covered with manual tests are now covered with functional/contract tests - it's easier to track it thus then with the use of the links on Jira between the ticket with a manual test case and e.g. the one concerning the creation of a contract/functional test. This could be helpful in making next steps in test automation, e.g. to determine the priorities - for instance, to tell which functional/contract test should be created first. Also, probably this could help the person who would be creating such an automated test - they could check whether there is e.g. an automated test for a similar feature created already, and look at the steps contained in the manual test case, which also could be some tip on how to write the automated test. But if you think that marking the manual test cases with the labels/keywords concerning automated tests is not necessary, I will exclude those keywords.
All in all, in my view, adding such a custom field to our Jira would quicken looking for suitable manual test cases greatly - I think that after introducing the field and marking the test cases, searching for manual test cases concerning a given feature would take up to 5 minutes, even for a person who is not familiar with our test cases.
The current list of keywords is the following:
- Adjustments
- Alerts
- Automated
- Calculations
- Catalog
- CT
- Email
- EmergencyRequisitions
- Facilities
- FacilityTypes
- FT
- GeographicZones
- ISAs
- Login