You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
In BigPicture, apart from the Jira issue, you have the possibility to create a basic task. It's easy to create, simply by clicking the “+” button in the top-left corner of the Gantt module. The 'Basic' label helps to distinguish BigPicture native tasks from Jira tasks.
In the context of BigPicture and BigGantt, basic tasks and Jira issues coexist under the same conditions. For example, you can establish a dependency in BigPicture between a basic task and a Jira issue, as shown in Figure 3.
Figure 3. Basic tasks and Jira issues behave almost identically within BigPicture context, for instance, they can be interconnected with dependencies in the Board module. Note the ‘Some basic task’ card interconnected with the PP-7 Jira user story.
These are the most common ways users leverage basic tasks in BigPicture and BigGantt:
In addition to accessibility, there is another benefit that BigPicture basic tasks offer over Jira issues - the possibility to group basic tasks into templates/project drafts. We have noticed that many Product/Project Managers prearrange the ‘Analysis – Development – Testing’ sequence.
Figure 4. Create templates for new projects consisting of basic tasks.
Using basic tasks allows quick configuration of this micro-structure in the Gantt chart/Roadmap timeline and then gradually hook up Jira tasks to the three parent tasks as the project takes shape in figure 4.
Basic task or Jira issue?
Given the option of basic tasks and Jira issues, what to use and when? The basic task is probably more practical than a Jira issue, when:
Basic tasks do not inflate the Jira backlog. Moreover, basic tasks are quicker to set up, more flexible to operate in BigPicture, and capable of being “parents” to other tasks. They are designed for planning and scheduling work.
There are 2 options for creating a new basic task: Create task > Basic task or Create sub-task > Basic task? What are the differences?
In the former scenario, the newly created basic task will be a brother of the currently highlighted task; while in the latter case, the newly created basic task will be a child of the currently highlighted task.
It is pretty easy to delete the basic task once it has fulfilled its role; just highlight the task to be deleted and press the trash button as shown in figure 5.
If you like the simplicity of basic tasks, test the objectives available in the Roadmap module. Similarly to a basic task, all you need to do to set an objective is to press ‘+’ button and enter a name for the objective. No need to fill a dozen Jira fields. The objective is another BigPicture native, business-oriented item – an alternative to engineering, development-biased Jira issues.
Figure 6. Creating an objective in the Roadmap module of BigPicture. The ‘Artificial…’ placeholder stands for what artificial tasks once were. Note that the Roadmap module was relabeled to ‘Objectives’ for the purpose of this Smart house SAFe ART Box.
104 accepted answers