Jacob Vu Rising Star

Hi @Michael Bialas Out of the box, I don't think there's a good way to do it unless you want to have a Kanban board in one project that ties into the other projects. Advanced Roadmaps (comes with Premium) would be a good option for you as you'd be able to create programs.

Hi @Seethalakshmi Muthuraman Can I ask why you want to automatically move tickets from open -> in progress? If you're looking to create statistics on how long tickets are in the different statuses, this wouldn't work. Also, this would imply that tickets are being worked on right as they're created, which could potentially…

Hi @aligntechsupport Are you asking how to check if tickets have been added to the plans you've created in Advanced Roadmaps? Like an audit log?

Hi @Sowmya V Are you looking to use the simple roadmap feature? A Jira admin would be able to enable it for your project board but as Jack mentioned, Advanced Roadmaps is a great tool to use for creating roadmaps.

Hi @Marvin Brand You'd be able to use Advanced Roadmaps to complete resource and capacity planning. It comes out of box with Jira premium but if you're on Jira standard, this means upgrading. Advanced Roadmaps would be able to help create roadmaps and gantt charts though, so that's also another useful feature that you get…

Hi @Betul Erdogan When you use a Jira query to import issues in, does it synchronize? It might be that components aren't global and there could be something happening with components specifically. Jacob 

Hi @Angela Stephens Are you asking about using Jira natively as a project management tool?

Hi @Moshe Boruchov You can do that via an automation so that when a ticket transitions to a production status, it'll send an email notification. Jacob

Hi @Lisa Zanini You could create a filter with JQL and then use it in a report/dashboard to help you. Something such as: "status was Testing AND status = Working" Jacob

Hi @Perri Strachan This can be done via the field context settings. Take a look in your project's settings and it should be there. It'll allow you to configure fields and determine whether or not they're required. Jacob

Hi @David Huang I'd suggest checking the groups and roles that the user is in and whether or not they have the appropriate permissions. They might be part of a role that's being excluded. Jacob

Hi @Angus Beath You can do this with a validator - you'd create one to check if the current user is the one raising the ticket and if so, they can't approve their own tickets. Jacob

Hi @Douglas Oliveira You can limit their access to one page through "issue-level security", I imagine. If you attach security levels to some of the issues then that could work but otherwise they'd have access to all project pages. Jacob

Hi @Salma Iz Are the teams working in the same Jira project or working on the same project? If they're just working in the same Jira project then I think that would be fine, you'd be able to separate their work in BigPicture with their own schedules. If they're working on the same project, I'm not sure how that would work…

Hi @Pawel Bah I'm a PM and track projects/products using BigP so hopefully I can provide some input here. I think it's still better to separate teams into individual Jira projects as it's easier to manage work for them without the need to use components. If you want to reduce the amount of projects that you have, teams…

Hi @Douglas Oliveira You could create groups with the clients that only provide them with permissions to follow their individual projects. They would need a Jira license in order to access Jira though, Atlassian doesn't offer "guest features". Jacob

hi @Thomas Wäspi You could create a group and allow them to only have the 'Browse Projects' permission in that single project. From my understanding though, they would need a license in order to be able to use Jira - there's no guest features at the moment in Jira. Jacob

Hi @Chris Black Have you looked in your settings to see if the view that you've created is 'private' or 'public'? If it's private, change it to public so that others can see it. That should help with sharing the view to different users.

Hi @Abulfaz Shukurov Have you tried using project roles so that different roles have access to different boards? Jacob

Hi @Özge K_ , have you tried looking into adding a condition in a workflow so that it can test to see if a user has the right approval to transition the issue? Jacob

Hi @[deleted] You should be able to link work from different projects under the same story/epic using the Link Issue feature. There's no need to use a third party app for this functionality as it's out of box. Jacob

Hi @Nitu Kumari To add on to what Clark's saying - if you are using company-managed projects, create a board with all of the projects that you want to have the plan for. Then you should enable the 'roadmaps' feature so that you can create a roadmap for all of the issues in those projects. That should be able to help you…

Hi @Dennis_H Have you thought about using the Roadmaps feature if it's available to you? This would help you create roadmaps (with start/end dates) based off of boards that you have. Jacob

Hi @Pham Van Hung Are they associated with the same board and do they both have the same start and end dates? J

Hi @Lisy Kane You should be able to create teams in Advanced Roadmaps. If the floating resources are consistent and are grouped into teams, I'd suggest creating teams for each group of resources so that you can assign them to various tasks/projects. J

Hi @Anstey.Bligh Plans are created based off of filters / boards, etc. If you're adding the issues to the board, they should be populating in the correct plan in Advanced Roadmaps. J

Hi @luisrieke A Product Owner is responsible for prioritizing work in the backlog and defines stories for their team - they understand why they need to build something and what should be prioritized over another. It's partially organizing work but part of it is providing insight into why developers need to build certain…

Hi @Chauvin As Nic mentioned, it's easy to implement it if you're just looking to install it. In order to get your organization on-board and using Big Picture effectively, that is much more difficult. Big Picture relies on good data from Jira and so you need to make sure you have structure in place to allow for that. J

Hi @Ephraim G It might be that they don't have the right permissions to do so. Double check your permissions for your users and see if that's what's wrong. Jacob

Hi @lucale So this is an issue with using the base hierarchies in Jira - you only get 3 levels of hierarchy and sub-tasks don't necessarily show up in epics. You'd have to use labels and components to get them to show. If you're looking to seriously manage projects in Jira, I'd suggest looking into Advanced Roadmaps, as…