![]() What is Confluence? Image: AtlassianĬonfluence is also developed by Atlassian. Jira is an excellent choice for users who need kanban or scrum support, perform sprint planning or need to have the agility to scale the software according to changing business needs.įor more information, read our full Jira review. However, it is also commonly used for other project management applications. Jira, a product by Atlassian, is popular with software development teams as it offers outstanding bug-tracking and issue-tracking capabilities. Should your organization use Jira or Confluence?. ![]() We also highlight how they compare in terms of core and advanced features and pricing and share some tips on which software to choose for your organization. In this article, we share the pros and cons of each software. While they are both designed to help businesses and individuals plan and track projects, they are very different tools. Jira and Confluence are two popular project management software. For more info, visit our Terms of Use page. This may influence how and where their products appear on our site, but vendors cannot pay to influence the content of our reviews. We may be compensated by vendors who appear on this page through methods such as affiliate links or sponsored partnerships. Use this guide to help you choose which is best for you. Covering their features, price, and more. This is an in-depth comparison of Jira vs Confluence. Confluence (2023): Which tool should you use? I saw a function/macro for that in the library, which is great.Jira vs. if the state of all sub-tasks change to the same state, the state of the story should be changed to the new state. Moreover, the states of the sub-tasks should be "rolled-up" to the contained story. ![]() Ideally, I would like to select if stories and/or sub-tasks are displayed in swimlanes. Lots of the tasks have similar titles, like "Write unit tests" or "Do code review", etc. If the sub-tasks would not show the containing story, but just ID, title and Epic name, the board would be a mess. Eg from TO DO to IN PROGRESS once a developer is starting to work on a particular task. That way, tasks can be moved from one board column to the next according to the workflow. I'd like to see the sub-tasks as "cards" on the board, with title *plus* (important!) the ID and title of its parent story. Not sure what the expected behaviour should be wrt what item types should be visible in the board swimlanes. > Only stories are visible in the board swimlanes. However, this had no effect at all.īased on our SCRUM process we did the following:ġ) Prod owners create stories in epics in the backlogĢ) Dev team estimates stories with Story Points (and T-Shirt sizes (added custom field))ģ) Scrum master creates sprint and sets start and end datesĤ) During sprint planning call, pull stories from backlog into active sprintĦ) Dev team breaks down stories in active sprint into sub-tasks and assigns them to team members ![]() See screenshotģ) The Swimlanes setting of the board, "Base Swimlanes on", was set to "Stories", which was the default.Ĥ) I tried to change the Swimlanes setting "Base Swimlanes on" to "Queries" and added the following JQL: "issueType in (Story, Sub-task, Task, Bug)". None of the sub-tasks are visible in the Board.Ģ) The sub-tasks of the stories in the sprint have the property "Sprint" set to the correct value of the active sprint. See screenshot of a sample dummy story which contains 2 sub-tasks. The sub-tasks are contained in their respective stories (which are part of the sprint) as expected. Thanks for your responses - really appreciated.ġ) The stories in the Active Sprint have been broken down into sub-tasks AFTER the stories have been assigned to the Sprint. I saw some state automation for stories and tasks, like to change the state of a story when all sub-tasks state have changed, etc). So, conceptually, how would one work with stories and sub-tasks in a scrum board?ĭo I have to enable some automation (e.g. You have to click on a story to see its sub-tasks in the pop-up window. However, the Active Board showed only stories. We created a sprint, pulled some stories into the sprint and started the sprint. Stories have been broken down into sub-tasks. Workflows, types, states have not changed. Only a few custom fields have been added. However, seems like you only can work with stories? Is this by design, or is there some configuration for sub-tasks in Boards?Īll Jira configuration is pretty much out of the box (I think I used Agile/Scrum template). Using the Scrum Board, we'd like to work with sub-tasks rather than stories. We're using Jira Cloud and just started a project a few weeks ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |