These are for small educational projects (websites, animations, videos, powerpoints, multimedia, etc.) for a university. We have 5 team members who are typically working on 1 to 10 small projects at any given time. Currently I track the status of each project in one spreadsheet. Ideally, I would create a Kanban project for each project, but I can't figure out how to add a delivery date to a project and how to configure the dashboard so it's organized by delivery date, which is the driving force for these projects.
Projects don't have data like that. They're generally expected to have many releases and track which issues are released by using versions to batch them up.
You could re-organise your JIRA so that it works off versions and a smaller set of projects, and do something with Kanban boards meaning you wouldn't need to continually recreate projects and boards for every new project.
Or, you could do a little bit of coding. Create an issue type for "project", and place one of these in a project every time you create a new one. Stick the date(s) on that, and then code something that cascades the date out to the issues somehow.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs