As the Industry Dive team grows, managing requests has become increasingly important to make sure everything is accounted for and not forgotten. Because of this, I recently worked on the Industry Dive support page to handle all internal requests for the Tech and Design teams using Jira issue collectors.
Role: Designer/Front-End Developer
Team Members: Tony Bagdon, Project Manager
Teams at Industry Dive, specifically Tech and Design, were receiving one-off requests frequently via Hipchat, an internal messaging system, and email. The requests were hard for teams to remember and keep track of. Because Industry Dive switched to Jira about a year ago for project management and ticket collection, the tech team’s project manager, Tony, decided we would use a Jira issue system. But, each team was still receiving one-off requests that they would then manually enter into the Jira system. How could we use Jira to improve this process across multiple departments?
First, issue collectors were created for both teams. Each collector has different form fields (i.e. description, due date, computer/browser type) depending on the issue type. By making each issue collector “custom” in Jira, I was able to manipulate the functionality of each button therefore making it easier to add multiple issue collectors to one page.
After adding each issue collector to one central page, all departments could now access the page and make requests from Tech and Design.
As for the design, I first tried just putting all issue collectors on the page with small descriptions for each type. I also added gifs to try and differentiate the request types.
While that was fun, other departments were often submitting requests to the incorrect issue collector. I decided the best and most scalable design was putting the designated issue collectors under each department name with additional help text for each department’s issue collectors. This way, users would know which team their request was going to.
Recently, I added issue collectors for the Sales Ops team and hopefully, because of the scalable design, more teams will be interested in adding their own collectors to manage their ongoing projects and requests.