2 Improving answer as per comments. Thank you.
source | link

I think it depends on the quality level you or your company want to accomplish.

It's a good practice to create bug for something is not related to code. I think it's even better to create some other bug 'project' related to these kind if issues.

By this I mean that we often use bugtrackers like Jira or Bugzilla only to manage bugs related to code. So, maybe that's why it feels strange to create a bug that are not related to code.

But we could have different kind of issues in other areas of software development, e.g. Documentation, Requirements, Process.

So we should leverage these trackers to manage these other kind of problems. You can create divisions or 'projects' in these tools to manage bugs in different aspects of the software development process.

So you could create a 'project' in your bug tracker related to that 'delayed job restarting' problems that you had. This way, you wouldn't mix this bug with code bugs in the bug tracker.

I think it depends on the quality level you or your company want to accomplish.

It's a good practice to create bug for something is not related to code. I think it's even better to create some other bug 'project' related to these kind if issues.

I think it depends on the quality level you or your company want to accomplish.

It's a good practice to create bug for something is not related to code. I think it's even better to create some other bug 'project' related to these kind if issues.

By this I mean that we often use bugtrackers like Jira or Bugzilla only to manage bugs related to code. So, maybe that's why it feels strange to create a bug that are not related to code.

But we could have different kind of issues in other areas of software development, e.g. Documentation, Requirements, Process.

So we should leverage these trackers to manage these other kind of problems. You can create divisions or 'projects' in these tools to manage bugs in different aspects of the software development process.

So you could create a 'project' in your bug tracker related to that 'delayed job restarting' problems that you had. This way, you wouldn't mix this bug with code bugs in the bug tracker.

1
source | link

I think it depends on the quality level you or your company want to accomplish.

It's a good practice to create bug for something is not related to code. I think it's even better to create some other bug 'project' related to these kind if issues.