I use jira, I do not use points, sprints, scrums, etc
Jira doesn't require those features. My workflow is "Ready, On Hold, In Progress, Done". It's a glorified task list with assignees, tagging, emails etc, that's corporate-wide -- no need to get random people to get accounts, everyone has one. All over our documentation and configs are references to "TKT-1234", which explains the background to a specific thing far more than an inline comment could.
It does the job just fine, I didn't need to jump through any hoops to get it working like that.
The alternate system engineers in other departments use is email. Tracking things in email is awful.
You can use Jira for far worse things, but that's not a problem with the tool, that's a problem with the culture.
Jira doesn't require those features. My workflow is "Ready, On Hold, In Progress, Done". It's a glorified task list with assignees, tagging, emails etc, that's corporate-wide -- no need to get random people to get accounts, everyone has one. All over our documentation and configs are references to "TKT-1234", which explains the background to a specific thing far more than an inline comment could.
It does the job just fine, I didn't need to jump through any hoops to get it working like that.
The alternate system engineers in other departments use is email. Tracking things in email is awful.
You can use Jira for far worse things, but that's not a problem with the tool, that's a problem with the culture.