Test QE Tracker creation Automation Rule

(Please make sure to fill all story details here with enough information so that it can be properly sized and is immediately actionable as per Our Definition of Ready
Ensure this story represents a small chunk of work that could be delivered within a sprint. If not, consider the possibility of splitting it or turning it into an epic with smaller related stories.
Before submitting it, please make sure to remove all comments like this one and fill in the release, epic and component fields of the story..)

User or Developer story

(One sentence describing this story from an end-user perspective.
As a [type of user], I want [an action] so that [a benefit/a value].)

Description

(Provide as much details as possible, so that any team member can pick it up and start to work on it immediately without having to reach out to you.)

Required

(...)

Nice to have

(...)

Engineering Details

(Any additional information that might be useful for engineers: related repositories or pull requests, related email threads, GitHub issues or other online discussions, how to set up any required accounts and/or environments if applicable, and so on.)

Acceptance Criteria

(Describe the goals that need to be achieved so that this story can be considered complete. Note this will also help QE to write their acceptance tests.)