Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Migration errors

Taoufik Karboubi
November 8, 2023

Hello;

I start my test migration, I have This errors in my attatchment file.

Best regards

1 answer

0 votes
Thomas Schlegel
Community Champion
November 6, 2018

Hi @greg,

what kind of board did you create? A scrum board or a kanban board? Or another type of board?

The answer to your question depends heavily on the type of your board.

greg
November 6, 2018

Sorry Thomas, I should have been more clear, it's a scrum board, and we're trying to adhere to all of the rules of scrum.

Also, I have just learned that it's acceptable to create sub-tasks from the stories, then the stories can move through the sprint with their sub-tasks. Then you estimate the sub-tasks using hours and can track your burndown against those hours, while you use the story points in your stories to track velocity.

That makes sense to me, does that sound right to you?

Thomas Schlegel
Community Champion
November 6, 2018

No problem, @greg.

In a Scrum backlog, you do not see subtasks at all, only stories. That's why I asked. The behaviour is different in Kanban boards, there you also see subtask in the backlog.

If you add a story to a sprint and start the sprint, the subtask will then be visible in the "Active sprints"-board.

In Scrum, subtasks won't be estimated, just stories. subtasks do not influence the velocity of your sprint. Only the storypoints will do (or time, or count, if you selected this in your board configuration). 

Like Tawana Thomas likes this
Thomas Schlegel
Community Champion
November 6, 2018

The tasks are independent of their stories within the Active-Sprint-Board. That means, you can move a sub-task to any other column, and if the last subtask of a story is done, Jira asks you, if the story should also be moved to done.

leonardonogatz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 19, 2023

I found this post trying to clarify my understanding about my work board. I thought at first like Greg, that in subtasks will be easier to the sprint have and end, a visual end on JIRA. But sometimes finish subtasks can no end a story, and the sprint is about a story (where we estimate). 
If I understand correctly, @Thomas Schlegel the end of a sprint should end a story(s)?
It is hard for me understand it cuz in my job we depends a lot of a third part work, sometimes the story never ends and I can't figure out where is the mistake. (I am just a developer but sometimes it bothers me).

Thomas Schlegel
Community Champion
January 19, 2023

Hi @leonardonogatz ,

stories should be finished within one sprint. I would say, long lasting stories are epics. These are independent of the sprints duration and can last forever if you need them to.

Like leonardonogatz likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events