Ree Kent Atlassian Team

Comments

  • Hi @David Wuth , Per today's Cloud blog, this is in the process of rolling out. https://confluence.atlassian.com/cloud/blog/2022/01/atlassian-cloud-changes-jan-17-to-jan-24-2022 Filters: Collaborate easier with edit permissions No more copying and recreating filters just to collaborate. A filter's owner can give anyone on…
  • Hi Ryan, There are a few uses for this feature. One popular use is to mark that an issue is impeded by another. This is similar to using the blocks/is blocked by links, but the Flag feature adds coloring to the card to make it more visible. Also, if you have teams working across Jira projects with interdependencies between…
  • So sorry Laxmi, we are not experts on all the apps. You might want to reach out to the vendor at https://eazybi.com/contact Or, someone in the community may be able to help. Thank you, Marie
  • From what you have shared, you may only need one board. Typically if a team manages work via sub-tasks, the stories have a simple workflow - To Do, In Progress and Done. Once all the sub-tasks for a story are completed, the story would also be done. If you are using the simplified workflow, you would receive a prompt to…
  • Hi Benjamin, Since a sub-task is in part of a story, it is in the same sprint as the story by default. The definition of done usually applies at the story level and includes closing all sub-tasks. If there is a need to break up a story, to have it completed in separate sprints, you can use the clone or split feature to…
  • Hi Ryan, Great question! The main benefit is having fewer columns, allowing for more real estate on the board for cards. The downside to this is that users cannot transition issues within a column. Many teams prefer to have one status per column so that they can use the board to update statuses. However, this can make for…