I’ve been working with Jira for my project management needs and I have a dashboard that works really well for my team. Now I need to create a similar dashboard for another team but I don’t want to manually recreate all the gadgets and configurations from scratch.
Is there a way to duplicate an existing dashboard through Jira’s REST API? I’ve looked through some documentation but couldn’t find clear examples of how to copy dashboard configurations.
Alternatively, would it be easier to build a completely new dashboard programmatically using API calls? I’m comfortable with making REST requests but I’m not sure which approach would be more straightforward.
Any code examples or guidance on the best API endpoints to use would be really helpful. Thanks in advance!
you can’t just clone dashboards directly thru the api. but exporting configs is your best bet. get the existing one with GET /rest/api/3/dashboard/{id} then use POST to make a new one with the same gadgets. it’s kinda tedious, but defo better than startin from scratch.
Had this exact problem six months ago when we needed to scale dashboards across multiple teams. Here’s what worked for me: Use the dashboard API with gadget configuration endpoints. Start by grabbing your source dashboard with GET /rest/api/3/dashboard/{dashboardId} - gives you the basic structure. Then loop through each gadget and grab their configs via GET /rest/gadget/1.0/dashboard/gadget/{gadgetId}. The annoying part: each gadget type has different config parameters, so you’ll handle them one by one. Once you’ve got everything stored, create the new dashboard with POST /rest/api/3/dashboard, then add gadgets using POST /rest/gadget/1.0/dashboard/{dashboardId}/gadget. Don’t forget to update team-specific filters or project references in the gadget configs before applying them. Took me two days to script properly, but now I can duplicate dashboards in minutes. Way more reliable than clicking through the UI.
Been there recently and the programmatic approach saved me hours. There’s no direct clone function, but I used a hybrid method that worked great. Pull the dashboard structure with the standard endpoint, then write a script to map gadget types and properties. The tricky part is gadget positions and column layouts - they use a grid system that’s not obvious from the docs. I created a config template file to modify team-specific stuff like project keys and user groups before pushing to the new dashboard. Took half a day to set up initially, but now I can spin up new team dashboards in under ten minutes. Way cleaner than manually recreating everything.