Many product management teams live in a world scattered across tools. Google Docs for documentation, whichever tool the development team uses for task management, spreadsheets for planning, and some PowerPoint here and there for presenting plans to your stakeholders.
Coda provides a flexible surface for teams to consolidate their work together into a single place. And through Packs, Coda enables teams to pull data from all the other tools they use into a single unified Team Hub.
Whether your team plans in Epics and Stories, Features and Requirements, or any other type of terminology structure, Coda can easily be fit to match how your team works.
This doc provides an example framework for how a product team can centrally manage their work out of a Coda doc that pulls in development execution work from Jira through Coda’s
Next, go to the Coda & Jira page in the doc and click any of the Choose what to sync buttons, which will open up the pack configuration allowing you to select which Project you want to connect to, and optionally add filters to limit the quantity of issues pulled in.
Note: It is strongly encouraged to filter the pack in order to ensure you are only bringing in the Jira Issues you want within your doc. Jira Query Language (
) can be added as an import filter option by clicking + Add criteria.
Buttons, Formulas, and Filters
Progress Formula: The progress formula on the Epics page will need to be updated based on the statuses for your Jira Issues. In the template, the formula is set to count the number of records in the “Done” status. This will need to be changed to whichever status your team uses to mark work as complete in Jira.
2. Filters: The interactive filters on the Coda & Jira page may need to be updated if your issues do not contain an “Assignee” or “Status” field. Simply right click the filter and edit the formula in the Selectable Options field to match your Jira Issues.
3. Buttons: The Submit button from the Feature Requests page will need to be configured to send to create Issues in the correct Jira project, as well as send values for the required Jira fields. Right click the button to add these configurations. Note: You will need to add options to the button for every Jira field in order for the button to work. Non-Required fields can have the option value left blank.