Settings and activity
12 results found
-
16 votes
Alison
supported this idea
·
An error occurred while saving the comment -
3 votes
Alison
shared this idea
·
-
1 vote
Alison
shared this idea
·
-
1 vote
Alison
shared this idea
·
-
1 vote
Alison
supported this idea
·
-
2 votes
Alison
supported this idea
·
Alison
shared this idea
·
-
8 votes
Alison
supported this idea
·
An error occurred while saving the comment
Alison
commented
Agreed. It is annoying to open another window in order to find the issue number. If this could work in the same way as the traceability by using the 'show issues' feature.
-
26 votes
Alison
supported this idea
·
An error occurred while saving the comment
Alison
commented
We don't use JIRA but it would be useful to have a new issue automatically linked to requirements so that we don't have to do it manually each time.
Then when we are in the requirements screen we can see all the linked tests and their execution status AND all the issues linked to those tests. -
1 vote
Alison
shared this idea
·
-
3 votes
Alison
supported this idea
·
An error occurred while saving the comment
Alison
commented
I support this. As well as the option to add it at test set, instance or run level depending on whether the data is shared across all tests, or not.
-
6 votes
Alison
shared this idea
·
-
13 votes
Alison
supported this idea
·
When performing repeatitve testing with step permuatations, it takes ages in the new UI to add the same test into a test set multiple times.
It would be useful to have a 'number of copies' option.
Select the test - add to test set - number of copies = 20
Then 20 instances of the same test are added to the test set