<?xml version="1.0"?>
<rss version="2.0"><channel><title>Stories: Stories</title><link>https://beta.jimiwikman.se/resources/stories/atlassian/720_atlassian-general/782_atlassian-development/?d=32</link><description>Stories: Stories</description><language>en</language><item><title>How I built a Forge application to map teams to boards in Jira</title><link>https://beta.jimiwikman.se/resources/stories/atlassian/720_atlassian-general/782_atlassian-development/how-i-built-a-forge-application-to-map-teams-to-boards-in-jira-r2173/</link><description><![CDATA[<p data-pm-slice="0 0 []">
	I previously <a href="https://community.atlassian.com/t5/Jira-articles/How-I-built-a-Forge-app-to-keep-Jira-issue-hierarchy-in-sync/ba-p/2455910" rel="external nofollow" target="_blank">published a post about a Forge application that I’d written called the "Issue Status Helper"</a> and thought it might be useful to share another example of how I've used Forge to help Jira meet our specific project management needs.
</p>

<p>
	This application has a number of similarities with the Issue Status Helper application but touches on a few different modules and capabilities that are worth exploring. In particular these are the new and improved UI Kit, Jira Custom Fields and GraphQL.
</p>

<p>
	The application is called “<a href="https://marketplace.atlassian.com/apps/1235496/jira-board-buddy?hosting=cloud&amp;tab=overview" rel="external nofollow" target="_blank">Jira Board Buddy</a>” and allows you to map teams to boards for a project and enforce that mapping for issues within the project. First let’s dive into the problem that I was using Forge to solve…
</p>
]]></description><guid isPermaLink="false">2173</guid><pubDate>Fri, 11 Oct 2024 06:05:29 +0000</pubDate></item></channel></rss>
