We continue a series of blog posts about our add-on Smart Attachments and integration of its capabilities into your JIRA workflow. Last time we had a blog post from the company that uses JIRA and Smart Attachments for handling requests to HelpDesk system.In this blog post we will present you with a new case study about a web studio that adapted Atlassian JIRA to their website designing workflow.
To avoid compromising the customer’s private data, we have replaced the provided screenshots with random user accounts.
Website Design Studio
Our customer is a mid-size web studio working on branded website projects for foreign customers. They use JIRA as a platform for tracking document, design, development and testing tasks. Most frequently tasks for different departments are created as one task, but all transitions across departments are done within JIRA workflows. It is necessary to point out that each step has a set of files that is attached to the issue. So each issue gets a plenty of files starting from page prototypes and finishing with multiple test cases. It is easy to imagine a mess of files that was kept in each issue.
The customer tried to resolve this by means of JIRA though creation of sub-tasks within the parent issue, but it required more time to create a separate sub-task for each department, and then review and close the task. Additionally, it caused exponential growth of projects in JIRA and several issues with platform performance.
After several attempts to find a solution to this problem, they tried to find some add-on that will help them categorize the attachments or group files by some attribute. But nothing suitable has been found in the Atlassian Marketplace.
After googling they found a case study of a custom add-on created by our company. This add-on allowed you to choose which files to show when you perform transition to the next issue step. The customer contacted our company and discussed with us a possibility to get this add-on. After some time the add-on was available for download in the Atlassian Marketplace as a commercial product.
So started their experience with Smart Attachments integrated into their workflow. They configured categories for each department involved into the website development. As usual, JIRA projects have the following categories:
- Requirements – one or multiple documents with the defined requirements for some website page or section.
- Prototypes – interface prototypes created by business analysts.
- Design – design mockups produced by designers based on the defined requirements.
- Development – page code developed by developers. Some customers prefer to validate the written code themselves.
- Documentation – documentation for the developed website functionality.
Categories allow the users to quickly find the required file for any department at a definite moment of development. In some projects, the customer allows customers to log in to JIRA and view the design prototypes. This became possible with theaccess permissions available in Smart Attachments. Now they can easily delegate the appropriate permissions to any user, group or project role. The newly added capability to upload multiple file revisions helps the design team to preserve order in issues and the rest of users to view the latest design revision.
Users can upload files to categories while performing transitions to the next workflow step or just by the simple dragging to the appropriate category when viewing the issue.
The customer also uses the renaming of attachments as in most cases people upload files without user-friendly names, so it was a nightmare to upload files again with normal names. Now they can always rename an attachment and add a commentabout the document even when it is uploaded.
To try the add-on just visit its page on Marketplace and install the latest version. If you encounter any issues with Smart Attachments submit a ticket to our Helpesk system or submit your idea to our User Feedback system if some function is not available.