Is it possible to make it such that single-issues (stories without tasks) can be tracked the same way a story with one task can be tracked? At my company, stories with no tasks are put under "Other Issues". that creates the following problems,
- there is no swim lane to follow the work done, and
- work can't be vertically prioritized in the sprint (it sits at the bottom in Other Issues)
But solving that problem includes some combination of complexity where you create a redundant story or a redundant task just to get that functionality (ie, the task is a clone of the story, or the story is a clone of the task). This is all the more crapola because the process of cloning to do that doesn't carry over the BitBucket code-tracking (which is done by story number which changes for the cloned issue), and it also doesn't carry over the Testing Steps. And even if it did, it creates two places for everything to be updated. So if we unwind what we're doing the reason we seem to be doing it is the above two points, and I wonder if there is not a better way to do this in JIRA?
I'm envisioning each task without a story (or story without a task depending on how you look at it), getting its own bucket with its own swim lane, or something like this. I was just curious to know what if anything is possible to solve this. Currently in our workflow it seems stories without tasks, or tasks without stories shouldn't be permitted.