Used the issue type Task to represent feature/Requirements

[Gilles Momo]

We would like in our project to use the issue type Task to define functionality or requirements. So that we can directly connect a test to a task and see the test progress or coverage on a task. How can we configure this?

[Bernhard Doleschel _Ease Solutions_]

Hello @Gilles Momo ,

I´m Bernhard from Ease Solutions, the vendor of R4J - Requirements Management for Jira. 
Using R4J for Jira Server/Data Center (on premise) edition will create automatically some requirement issue types you can link to your test cases. The edition for Jira Cloud don´t support this yet, but the manual creation is an easy step for the Jira administrator.

With our app (as an extension of your Jira system) you can easier gather and manage requirements within Jira. So your data stays there and can be used for any other Jira purpose. R4J helps you to 

• Organize the Jira issues in a readable tree structure
• See the dependency in a coverage and traceability view between each other, the development tasks, epics and stories and also test/verification issues
• Identify changes by the revision details
• Notify task/test owners when a linked requirement changes
• Baseline (and diff) your features for each milestone
• Export your requirements in a document based on your corporate template

If you like to learn more, you are welcome to join our public demos

• For Jira Cloud edition
• For Jira Server/Data Center edition

Best regards,

Bernhard from Ease Solutions

[Joe Pitt]

First, I would create a new issue type named 'Requirements' and use it. You can then link the issue to the test.  If you use Task that could become confusing if you really wanted to have tasks entered as the task issue type. I can't speak on how to show test progress. It may be possible in a dashboard gadget. As for coverage, Jira doesn't work well creating RTM reports.