What we wanted to accomplish with Copy & Sync was nothing short of complete peace of mind. The peace of mind of Jira admins, first, who can always be sure that their tools will be handled by their users exactly as they are intended to. The peace of mind of the Jira users, then, who will be guided every step of the way in their work, and free of any repetitive tasks they had to perform until now.

What inspired us was watching our own support agents struggle daily on tasks that were an inefficient use of time for them. Their expertise was in the help they could provide to our customers, not in their ability to copy Jira issues from one project to another, or manually sifting through information to select what would be relevant to our developers.

What it does

That's where Elements Copy & Sync can be particularly useful. After a couple of simple configuration steps, our copy recipes can be used across any Jira Cloud instance by all types of users. No matter if Copy & Sync is used by beginners or more experienced Jira users, the result will always be the same : issues will be copied where they are supposed to, with the exact information needed, whether it's included in the issue context, in comments, or in attachments.

As different Jira projects often require completely different actions, Copy & Sync Cloud recipes can be customized to any situation. Jira admins have the complete control over where the copies can be performed by users, for instance in a given project only, or for a couple of issue types in a specific status, or even for issues with a distinct label and priority. The same level of guidance can be applied to what is copied, and where it will be copied to.

How we built it

Our team strives to always look at new technologies, so with that in mind we opted to build our application with React (Redux-Saga) and Typescript for the front-end. The back-end runs on Java, Spring Boot and JPA.

Challenges we ran into

An interesting challenge we ran into was using the Jira Cloud API for the first time. Until now, our team had only worked on Jira Server/Data Center, so discovering what is (and more importantly, isn't) possible to do in Jira Cloud had its share of surprises.

Accomplishments that we're proud of

Setting apart a few setbacks, we are really proud of what we were able to accomplish in such a short amount of time. Not only were we able to complete the features we were hoping for in time for Codegeist, but we had time to add even more, in a good-looking package we are actually very proud of.

What we learned

We discovered that our little team worked really well toward a common and clear goal and that we were able to help one another every step of the way. With a full Agile development process, we were able to increment little by little on our features and what our app was bringing to the table, while always having a product we felt we could release on a days notice.

What's next for Elements Copy & Sync

We still have a few features we want to implement before going public with our add-on, but in the meantime we are quite happy that some people will be able to discover it, and hopefully enjoy it, right now.

Built With

Share this project: