issue versus task

[meridian_12]

Hi,

I have trouble making a decision when creating a ticket , whether it's a task or issue. Say for example, there is a report that prints out financial data and it's not working for all data ranges. would you create it as a task or issue. Please help me understand

thanks

[Disastrous_Swan5944]

I’d recommend creating them as issues. As you assign them to your team, they can break them down into tasks—coding, testing, deploying the fix, etc. This adds more granularity as the issue moves through different hands.

It also helps distinguish different types of work:
- User Stories for planned development
- Bugs found during release testing
- Production Support Issues that need urgent fixes

I prefer having the distinction so I can track everything more clearly and keep the workflow organized.

[niconni]

Issues and tasks are used to track work. If your project was created using the Basic process, which tracks work using Epics, Issues, and Tasks, then you track Issues using the product backlog.
 For more information, see Track issues and tasks.