That could be a valid way of representing what you're doing. For most, it probably is not. On the most part, people will use a Jira project to represent a collection of tasks that should be considered together. This might be because they need to work the same way, the same team will work on them, they represent a product or system, and so-on.
There's no solid one "best" way to use Jira and its project/issue/sub-task break-down, it all very much depends on what you're doing and why.
Hi Luciana,
If you are locked-in to this use of Jira, I think you will find it very helpful to be well-versed in being able to search for specific groups of issues: https://confluence.atlassian.com/jirasoftwarecloud/searching-for-issues-764478280.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.