@Tetiana Honcharova Every card has a unique ID which you can find in the URL, that's the most obvious choice.
What is the workflow you're wanting to achieve?
Thanks for reply.
Well it would be convenient if there would be the way to mark somehow sprints and the tickets inside relayed to sprint. I mean automatically and in addition to sprint name which is created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Tetiana Honcharova Perhaps you could have one card per sprint, and one board for each sprint card linked to the card.
That way you'd have an overview board which showed all your sprints, and could drill down to the cards for each sprint.
You would have your backlog on the overview board, then move cards from there into the current sprint board (maybe with some interim lists while planning) and then you'd have stages for the sprints to go through in order to be deployed.
Any cards that didn't get done from a sprint board could move to the backlog again, and the sprint cards would sit in a "Done" list, maybe with the completed due date showing when they were deployed.
A next logical step would be to automate all of that to reduce manual clicking and dragging, and to perhaps provide automated reporting on the overview board to indicate the current status of the sprint
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.