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.
I'm new here, so please forgive me if this is a basic use error!
I've set up our business' global task list (everything we need to get done). My intention was then to use each of those items (issues) to generate a new project.
I.E. One of the items on the to-do is a new product launch that we want to go live with by Q3. Now I want to create a project that can capture all of the elements of that task (And for the To Do item to mirror the project status (i.e. In Progress, Completed, etc). Not all tasks will be worthy of their own project though (i.e. Get New Coffee.) Is that possible, or do I need to rethink the relationships available?
Welcome to the Atlassian Community!
Just trying to understand the need to create separate projects for each task. Might I suggest a different way of thinking of this. You could use the Epic-Task-Subtask relationship instead of creating individual projects for each task. This way, you would be able to track everything in a single project.
For example, you could have an Epic that is called Q2 Website Launch, and under that Epic, you would have your various tasks associated with that Epic:
Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.