What Things QA engineer should know about JIRA?

In this post you will know what things Testing engineer should know about JIRA. I assume QA Engineer here who knows how to test manually and using automated software tools such as Selenium.

With that assumption, let us talk about using Jira as QA Engineer testing manually :

JIRA is a tool that fit for every phase of product or project delivery in agile methodology.

1. You should know how to search requirements/Epics/stories/test cases/tasks/bugs etc . Using JQL queries
2. You should know how to write test cases and format them visually appealing. JIRA uses its own markup language to beautify the content in various formats.
3. You should know the relation between each task or issue to trace bidirectionally (traceability matrix)
4. You should know how to check whether a development task is completed,committed/merged to start your testing
5. You should know any external plugins installed to enhance jira capabilities to fit the project needs and how to use them
6. You should know how work flow of test cases/test runs/bugs are designed and how to progress them from one state to other.
7. You should know how to mention a user in comments/descriptions using @ symbol to communicate with in the jira
8. You should know how can add some information into jira by just sending an email (if this is condigured) this minimizes the time to create tasks
9. You should know how to filter sprints/releases a d create your own system and user dash boards to get a quick summary of whats going on.
10. You should know different ways to move a task from one state to other state(drag and drop or through status )
11. How to add screen shots with thumbnail or original size
12. Text formatting: headers, sub headers, list items, bullet points, italic, bold etc

AS an automation QA Engineer:

1. One should know how to execute the test cases with certain lable or tag in jira
2. Should know how to mark the test case pass/fail/hold etc using auyomation scripts
3. How to pull a summary of executed test scripts and create a dash board.
4. How to integrate jira into continuous integration and delivery pipeline and execute scripts through jira automatically.
5. Triggering automatic emails and alerts warnings on certain set SLAs when they meet or exceed or failed. For example,estimations of each story exceeds the agreed time lines, sprints spill over ro next ones