I’ve gone ahead and moved your thread to the #developersAPI category as API questions and bugs are handled independently in this category. My colleagues from the API Team or our experts will be in touch asap! Thank you so much for your patience
Yes, there doesn’t seem to be a story subtype for task creation, but I would have expected a story with subtype added_to_task (or added_to_project for a top-level task). That’s what I have been using so far to determine the actual task creator – because task objects only have the field created_at, but no field for the person who created it.
In my usage so far, this task was the only one out of several hundreds without any associated stories. Nothing else seems unusual or wrong with this task, though.
For testing as you suggested, I just edited the task description. A new story was created. But no other stories were created retroactively:
From the screenshots, the API is behaving correctly—these tasks indeed wouldn’t have any stories on them. The creation story is a fake in the UI, confusingly, but you can get the same information from the created_by and created_at fields as @Phil_Seeman pointed out. We do have a task internally to add created_by to the docs which I’ve pinged again, though I can’t make any promises as to when it will finally be live on our site.
Thanks! As for tasks that are part of a project but do not have any associated stories (see my initial post): Is that something one should expect to happen, or is that a bug? In my tests, this was the only task out of hundreds that didn’t have an associated added_to_task or added_to_project story.
According to the screenshot, the task is not in any project, so there wouldn’t be any added_to_project story. Additionally, a weird edge case/bug in our product (not just the API) is that the added_to_task story only appears if an already created task is turned into a subtask. If a task is created as a subtask to begin with, the story doesn’t get created. I suspect that’s what happened here: you have a task that was directly created as a subtask and so has no stories on it.
For fun, I just tried to create a subtask without an added_to_task story being created (TAB+S, clicking on the subtask icon, hitting return when editing the name of another subtask). But all of these actually did create a added_to_task story. Maybe the edge case/bug you mention has been fixed? But while playing with it I found the answer: The UI actually allows deleting system-type stories. When hovering over the “…added subtask to task…” story, a small x appears on the right side. My hypothesis is therefore that in the case I described the added_to_task was just accidentally deleted.
So I guess I can answer my own question. There was no bug in what I described, as it’s easy to delete all stories from a task…