hackathon_id
int64 1.57k
23.4k
| project_link
stringlengths 30
96
| full_desc
stringlengths 1
547k
⌀ | title
stringlengths 1
60
⌀ | brief_desc
stringlengths 1
200
⌀ | team_members
stringlengths 2
870
| prize
stringlengths 2
792
| tags
stringlengths 2
4.47k
| __index_level_0__
int64 0
695
|
|---|---|---|---|---|---|---|---|---|
10,045 | https://devpost.com/software/sumry | Login Page
Dashboard
Inspiration
In this highly uncertain time of CoVID-19, where no one knows what the future holds for us, we heard from our friends working in the corporate world how much they are disappointed with
online standup meetings
. They are spending a considerable amount of time in online standup meetings, which is hampering the whole lifestyle and productivity of a person.This can also induce psychological problems such as
depression and anxiety
, which are already “some of the greatest causes of misery in our world".
So, we thought why don’t we build something that can eliminate the very need for long standup meetings.
What it does
Sumry is an app that generates a personalized report, taking into account all the project related activities done throughout the day by each developer on BitBucket.
It shows their activities in a
graphical dashboard
which further saves time of the Product Manager as they are able to analyze each developer’s performance expeditiously.
Some Note-worthy features of Sumry -
Encourages transparency among peers.
Reduces unproductive man-hours.
Enlists & categorizes each activity done, all at a single place; saving you from a lot of hassle.
Doesn’t let your ability to justify yourself come in the way of your promotion. We help your work speak for itself.
Makes it easy to analyze the performance through data visualizations present on the dashboard.
How we built it
After analyzing the problem at hand, we conducted 2-3 brainstorming sessions. These brainstorming sessions helped us figure out the features to be implemented as well as the tech stack behind our product.
We ended up developing our web app using
ReactJS and CSS
. We used the
Bitbucket API
to authenticate and fetch the data of our users. We used the Material-UI library to keep our design consistent. Additional dependencies like Recharts, React-Player, Axios, etc. were also used. Sumry is an
open-source product
, thus we have used the prettier style conventional to style our code. It will make it easier for other contributors, from around the world, to read and contribute to our codebase.
Challenges we ran into
The bitbucket API offers limited data points for us to fetch and display on our website. This often made us change the working of our web app.
We wanted to build a product that worked efficiently in different time zones and different continents without giving trouble to our users. Hence, the 24-hour contribution time period of developers became very subjective. But luckily, we were able to find a workaround for it as well!
Another challenge was that we had never built a website before and so, more than anything, it was a great learning experience.
Accomplishments that we're proud of
We have built a product which has the power to save
countless man-hours
. It can be put to use, not just professional but also personally for systematic product development. Nothing is better than the feeling of building something which makes human life simpler.
Despite our usual schedule, we were able to pull it off — together, as a team.
What we learned
We learned to build web applications from scratch, that too in the span of a week!
We had the opportunity to talk to a Project Manager of a blooming tech-based start-up in India (they use BitBucket for development purposes). We learned about the problems that he faces and asked him about the feasibility of Sumry in his company and how we can fill the gap, using our product, to save his precious hours.
What's next for Sumry
On the similar lines of the daily report, weekly and monthly report features are also in the pipeline.
We are also working on developing an
unbiased algorithm
(adopting Machine Learning) that will be able to churn out a score based on the performance of the developer.
We will also give the Project manager - the option to download the individual reports in the form of PDFs.
Soon, Sumry will be able to take feedback from Program Managers regarding the performance of each developer. It will then analyze & log each feedback.This can also prove to be a potential metric at the time of appraisal.
Built With
api
axios
bitbucket
css
html
javascript
npm
react
recharts
Try it out
www.sumry.ml
github.com | Sumry | Fed up of lengthy standup meetings? We present, Sumry - a tool that produces a thorough report, taking into account all project related activities over the day by devs. | ['Hemant Gupta', 'Chirag Gupta', 'Rachit Gupta', 'Laxya Pahuja'] | [] | ['api', 'axios', 'bitbucket', 'css', 'html', 'javascript', 'npm', 'react', 'recharts'] | 58 |
10,045 | https://devpost.com/software/goal-setter | Goal setter macro
Date picker for Target date
Days left display
Dynamically generated SVG
Inspiration
This macro displays a Goal setter block for atlassian confluence. An SVG image is generated which displays the remaining number of days. The user can also edit the target date using the macro configuration settings.
This macro will be very useful to keep track of important deadlines and provide a visual reminder for everyone with access to the page.
What it does
It takes a user input of "Target Date" and calculates the remaining number of days. It dynamically generates an SVG and displays it.
How I built it
I built this using Atlassian Forge. The macro is deployed on Confluence server. The macro is coded using node.js/typescript.
Challenges I ran into
Forge UI elements did not allow adding custom CSS, however I found a workaround by creating dynamic SVGs.
What I learned
I leant working with Forge API, UI elements and also deploying apps to various atlassian platforms.
What's next for Goal Setter
I want to give the user options for customising the information displayed.
Built With
atlassian
forge
node.js
Try it out
bitbucket.org
atlas-maker.atlassian.net | Goal Setter | Goals setter for Atlassian Confluence. This macro shows the remaining number of days for a target in Atlassian Confluence. | ['Jayshree Anandakumar'] | [] | ['atlassian', 'forge', 'node.js'] | 59 |
10,045 | https://devpost.com/software/glossary-helper | A section of complex words and terminology picked up from the article is placed at the bottom.
Inspiration
Simple but valuable - there is nothing more frustrating than reading through a critical wiki post that is flooded with complex terminology or industry-specific terms. Rather than forcing your readers (or new employees) to look up every term, add a quick glossary at the bottom that spells out exactly what you mean.
What it does
With a simple
/glossary
command in your Confluence article, our Forge app will insert a glossary section at the bottom of your article. The glossary includes the most commonly used complex words in the English language, and allows you to add or create new definitions as well.
How I built it
I used the Forge Typescript library along with a public dictionary listing online to build the app.
Challenges I ran into
It took me a bit to figure out how to work with Forge and debug issues that were happening. Overall, it was not a difficult experience.
Accomplishments that I'm proud of
I've used AWS Lambda a lot and it was really cool to work with another serverless technology. Forge solves a big pain point for building apps which is infrastructure and security, it's great to work with a new system that attempts to solve these.
Built With
forge
node.js
typescript
Try it out
github.com | Glossary Helper | Add a quick footer to your Confluence article that finds complex words in your post and automatically inserts a definition at the bottom for your readers. | ['Joel Barna'] | [] | ['forge', 'node.js', 'typescript'] | 60 |
10,045 | https://devpost.com/software/slas-elapsed-time | Glance open
Many cycles sum up
SLAs Elapsed Time is an app built for Jira Service Desk using Forge.
Inspiration
We learned that some companies need to know the SLA elapsed time instead of remaining time. The data is available in Jira, you just need to do the math and count elapsed time by yourself. However, when the ticket went through many SLA cycles, it can be tedious.
What it does
SLAs Elapsed Time provides a glance panel in which all issue’s SLAs are listed, but instead of presenting remaining times, you will see elapsed times.
How we built it
SLAs Elapsed Time is built with Forge. It uses issueGlance glance module.
Challenges we ran into
It was fun to built the app in Forge. We missed the possibility to use styles, especially different fonts sizes and colors, but it turned out that the lack of those features does not influence the readability of the information.
We haven’t found any way to display the glance conditionally. The panel is dedicated only for Service Desk projects, therefore it would be better to display it based on project type.
Accomplishments that we are proud of
We learned how to use glance module in Forge and count elapsed time from /rest/servicedeskapi/request/$issueIdOrKey/sla endpoint.
What we learned
It is the 3rd app overall we have created in Forge. It was fun and challengeable to design the panel with a limited set of components.
What's next for SLAs Elapsed Time
The ability to export the list of relevant issues with elapsed times to csv and other formats is important to our customers. Exporting a set of issues would save a lot of time and effort to collect the data by hand.
At the moment, we couldn’t find a suitable place to generate such report, but we have some ideas in mind. We could implement JQL-based searcher placed at the bottom of the panel, which would let you set the range of issues to be included in export with the elapsed time computed.
Built With
forge
glance
javascript
jira | SLAs Elapsed Time | Learn the actual time your agents spend to resolve a ticket. View elapsed time instead of remaining time and let the app do the math! | ['Jarosław Morawski', 'Maciej Dudziak', 'Aleksandra Bosacka'] | [] | ['forge', 'glance', 'javascript', 'jira'] | 61 |
10,045 | https://devpost.com/software/behavest-4m7g69 | deleted deleted
Built With
deleted | deleted deleted | deleted deleted | [] | [] | ['deleted'] | 62 |
10,045 | https://devpost.com/software/security-encryption-for-confluence-cloud | Securely store confidential information
Client-side decryption and encryption
Allow/deny access list by users and groups
Centralized secrets management
Inspiration
We've all heard stories about passwords being passed around in plain text, through emails, chats, or... sticky notes. It's super convenient, but pretty sure your InfoSec team won't be happy with it. And for most, Confluence is the go-to information repository, yet things may still be saved in plain text... so, WHAT IF we can make it both secure and convenient?
What it does
Let Confluence users to securely store secrets (confidential information, passwords, bank accounts, credit card numbers, classified reports, API tokens, etc.) using a macro in Confluence to encrypt and decrypt, store, manage and audit access to all of that. Centralized secret management so you can see and search for all secrets in a space at one go.
How we built it
We've got some lessons learned from our existing Server app, so it's time to take it to Cloud. With some support from potential users and some Atlassian Connect + Atlaskit + serverless + encryption (PGP, AES), we've got it working.
Challenges we ran into
Designing the data architecture was quite a challenge, considering that we try not to store any customer data on our servers and Confluence Cloud's storage options (content properties, app properties) are not exactly protected to just a single app.
Accomplishments that we're proud of
Dealing with encryption methods, data privacy... and of course, making it work!
What we learned
Teamwork makes the dream work :)
What's next for Security & Encryption for Confluence Cloud
It will be reaching the Atlassian Marketplace soon. We believe we have a great foundation for more powerful features to come.
Built With
atlaskit
serverless
Try it out
security-encryption.performancerocket.com | Security & Encryption for Confluence Cloud | Encrypt, manage & audit confidential information in Confluence Cloud | ['Azwandi Aris', 'Hazem Gharib', 'Brigitte L', 'Yong-Chong, Long'] | [] | ['atlaskit', 'serverless'] | 63 |
10,045 | https://devpost.com/software/meteor | Meteor
Beat Graph
Screenplay Macro
Screenplay Macro
String List Macro
String List Macro
Mutiny Games
Mutiny Games
Mutiny Games is an Australian independent game studio founded in 2019. Mutiny is building bite-sized video games and software tools that can be used to assist with screening cognitive health for symptoms of decline, such as those connected with dementia and other forms of dysfunction.
Combining engaging entertainment with health assessment is the first step in the process of moving the edge of healthcare from clinics into the home. The vision of Mutiny Games is a true fusion of art and healthcare. And we're here to make that happen.
We had a problem
However, we had a problem and it turns out a lot of other screenwriters do as well. There were no good ways to create screenplays for the games we want to make. So, we built Meteor and we are sharing it with other creators.
Hello, Meteor
Meteor is a web application that makes it easy to create interactive screenplays. This cloud-based platform is designed for the Melissa Mathisons and Quentin Tarantinos among us, as well as the hobbyist typing their opus on the weekends.
Screenwriters and developers can design story elements, write narratives and plan production for video games, TV shows or film with the tap of a few buttons using the ‘Beat Graph’ feature.
Meteor assists creators in writing multi-path stories in which the viewer can choose where the narrative goes. This special feature allows developers to capture and collect the viewer’s interactions with the final production. This information is collected programmatically in a standardised format and can be used to measure a viewer’s cognitive functions.
Plan, Compose, Produce and Examine
Meteor gives screenwriters and screen production companies peace of mind through its smart planning features, industry standard formatting and production templates. Compose and edit standard or multi-path screenplays (similar to Netflix’s Bandersnatch). Track all branching pathways with just a few taps.
Meteor’s unique and easy to use Beat Graph guides and helps writers with planning and writing each dramatic narrative event, action or decision beat by beat. The graph knows the Hero’s journey from the Ally’s journey, the point of a horror story is to be scared and what dramatic questions are.
Confluence Integration
Film production staff and game developers will be happy to find Meteor connects the dots to collaboration with Confluence integration. An Atlassian product already part of their daily workflow. Quickly insert a variety of live content from Meteor into a wiki page using easy to use macros for:
Screenplay Fragments
Cast Lists
Shot Lists
Location Lists
Costume Lists
Prop Lists and Set Dressings
String Lists
And More
A new class of content
Meteor is empowering screenwriters and game developers to create a new class of content and is set to launch sometime in the near future.
Built With
node.js
react | Meteor | A super intuitive way to write and produce interactive screenplays. | ['Simon Cullen'] | [] | ['node.js', 'react'] | 64 |
10,045 | https://devpost.com/software/customfield-pack | Showing the amount and traffic light status field
Thanks to the underlying issue properties, the mobile apps have basic support as well
Inspiration
As an Atlassian consultant, I'd love to carve customer's processes out on the Atlassian platform. This enables teams to be on the same page and even connect with teams that used to be disconnected with different systems and ways of working. Bringing the variety of customisations empowered by the open API is key in making Jira the center of the whole #digitaltransformation movement.
Going to the cloud, we see that many small but useful apps are missing: having to set-up and pay for the whole hosting infrastructure makes it impossible to let open source solutions thrive on the cloud platform.
When Atlassian announced Forge, this seems like a whole new beginning, making place for a whole new category of apps. When the Customfield module was added to Forge, it became clear that there was an opportunity that could be seized!
What it does
Installing the app will grant you new custom fields that can be used in your Jira instance:
Traffic Light Status: turns a red, amber or green status into a visual traffic light, ready to spice up some managerial processes
Amount: Start with a number and apply the typical currency formatting, making it immediately clear what the value stands for
How I built it
Getting started with Forge was a blast, following the tutorial got me started in no-time with the CLI and I created my project in my IDE of choice, IntelliJ.
The nice part is that this is a very simple one to implement, using only basic Javascript without any additional modules .
Challenges I ran into
Since the platform is young and rapidly evolving, things are not yet available or in heavy flux. Because Forge is built with a structure very similar to React, it is tempting to re-use React components - which don't work obviously :-)
The biggest hurdle was getting static resources in the app, in the end I settled with building svg inline. Unfortunately the auto-margin coming with the image-module can't be changed, leading the the traffic light being out of order. Hopefully in a later version, it is allowed to align those to the left as well.
Accomplishments that I'm proud of
Being able to build such additions with so few lines of code.
What I learned
I learned working with Forge, the ins, outs and possibilities out there for future product-building
What's next for Customfield Pack
This should be a start, not an ending. When Forge opens up, hopefully there will be a free tier for open source components. This would allow apps like this to be sponsored development with free (as in included in your subscription) hosting.
Built With
forge
javascript
Try it out
bitbucket.org | Customfield Pack | Bringing the well-known customisation power to Jira cloud and get your no-code projects started! | ['Tom Moors'] | [] | ['forge', 'javascript'] | 65 |
10,045 | https://devpost.com/software/developer-bookclub | Inspiration
I had the idea for this application when I wanted to hold a bookclub for developers that allows them to level up their skill in parallel to the work that they get assigned by the project manager.
What it does
It pulls a number of random developer focused (and soft skills focused books) from google books api that a developer on a jira project can then add as a task for themselves to read for the month.
How I built it
I built it using Forge and the issue panel, google books api and node.js, using forge ui for the components.
Challenges I ran into
Creating issues with jira v3 api was a bit of an issue and the limited documentation of forge due to it's beta status made creating the application difficult.
Accomplishments that I'm proud of
The application works and creates a jira issue that a developer can then use to track the books that they can read for the month.
What I learned
I have learned how to use forge to create simple Jira applications
What's next for Developer Bookclub
More books, more detailed tasks, adding comments and having discussions around the books teammates are reading
Built With
forgeui
google-books
node.js
Try it out
github.com
auth.atlassian.com | Developer Bookclub | Join your teams bookclub on Jira and level up as a developer! | ['Kacha Mukabe'] | [] | ['forgeui', 'google-books', 'node.js'] | 66 |
10,045 | https://devpost.com/software/jira-issue-progress | Display issue progress of linked issues
Display issue progress of sub-task
Configurable settings
Inspiration
While exploring Forge, we thought of creating issue reporting for end user. When working on an issue, end user might be interested to generate quick reporting based on its linked issues and sub-task.
This will help in visualisation of an issue's progress, especially when work is split up into different issues across projects.
What it does
Based on the user's defined list of issue type(s), issue link type(s) and number field, a chart will show the issue's progress for the number field across all relevant issues.
How I built it
Forge, JIRA, Node.js
Challenges
By using Atlassian Forge, it is easy to create apps on Jira Cloud without having to host any servers. This allows developers to experiment with new ideas and do quick demos.
But as Forge API is still under development, some functionality are not available. e.g. onChange, CSS, Text format, form validation, Issue Tab Panel etc.
Hopefully as more developers onboard and try out Forge, the API will have more features available.
What's next for Issue Progress for Jira
Linked Issue reporting by extending to other chart types like pie chart, bar graphs, line chart, roadmaps etc. The charting can also be based on other field types like date, selection etc.
Built With
forge
node.js | Issue Progress for Jira | To generate issue progress report based on its linked issues and sub-task. End user can configure report settings like calculation number field, colour, link types etc. | ['ZR T'] | [] | ['forge', 'node.js'] | 67 |
10,045 | https://devpost.com/software/transition-2 | Transition to accepted status
Issue created and transitioned to accepted status
Transition2 is an app built for Jira using Forge
Inspiration
Our daily work is based in Jira. In the workflow of our projects we use Triage and Open statues. When an issue is created, it goes into Triage status, then after accepted by product owner, it is transitioned to Open. Our boards are configured in a way that Triage is not visible in columns, so developers are not overwhelmed with the number of tasks laying in the backlog.
But there is one problem. When a new issue needs to go to the Kanban board right away (e.g. a major bug), you need to follow the frustrating ceremony: 1. Create an issue, 2. Open the issue, 3. Transition to Open. It takes a lot of time if you have to create several issues in a row.
In order to address this issue and increase productivity, Transition2 app has been created!
What it does
Transition2 app lets you set the target status of an issue right after it’s created. All you need to do is to add “Transition to“ custom field provided by the app to Create Screen and type in the name of the target status directly into the field.
How we built it
Transition2 is built with Forge . It uses customField and trigger module (avi:activity:created:issue) event.
Challenges we ran into
It turned out that Select component can’t be a child of CustomFieldView. Therefore we decided to use simple StatusLozenge to represent status in Issue View. StatusLozenge was hard to find at first, because it was renamed lately from Lozenge component.
CustomField component is not rendered on Issue Create, however the custom field is displayed based on its type. It allowed us to use the custom field module, however, the UI experience wasn’t the best. Nevertheless, instead of matching statuses by id or exact name, we decided to match them smartly, therefore there’s no need to worry about cases or spaces. In the near future we will try to match them also by status shortcuts.
During the implementation it turned out that you can’t set a default value on Forge custom fields. It is a pity as it would be great to be able to configure different issue types contexts and have various default values.
We also run into a problem with renaming the app or its custom field description. It turned out that once the app is installed or a custom field is created, you can change its name in manifest but the old values stays forever in some places, i.e. for custom field description - old description on Create Screen, or a name of the app when prompted to grant access. We decided to create a new app, this time with the updated name, and then swapped app.id in manifest to overcome such problems.
At the moment it is possible to transition issues only to the nearest status in the workflow. The reason is/issue/$issueKeyOrId/transitions endpoint which works like that. We haven't found an easy way to get all possible transitions for an issue type. Lately, new workflow endpoints have been added and we’re hoping to find a solution in the future.
Accomplishments that we are proud of
The app works well despite many framework limitations, the goal was achieved and we will for sure use it in our daily work in Jira projects.
What we learned
We have learned a lot even though it was our second app built in Forge. It won’t make sense to list all new modules and components we learnt, although a single noteworthy thing is that you can’t use impersonalisation in triggers. On one hand it surprised us, because the same is possible in connect. On the other hand, we can easily see the problem with showing the consent prompt to the user while a trigger is being executed. This makes writing automation much more harder if you don’t want your app to bypass user permissions.
What's next for Transition2
First of all we want to enable transitions to any status in the workflow if possible. Sometimes there is no straight transition between statuses and you are forced to change them one by one. Transition2 app will for sure help you with that. The next step would be handling the change of the status directly on the issue view (on edit).
We also want to have a glance module, where all transition are logged, similar to the history tab but with additional messages from our app.
We’re sure that with time, Transition2 app will evolve parallelly with the constant growth of possibilities in Forge.
Built With
customfield
forge
javascript
trigger | Transition 2 | Set the status directly on create screen, transition will be automatic! No need to follow complex workflow paths, speed up adding tasks to agile boards in a row just in a few clicks. | ['Maciej Dudziak', 'Jarosław Morawski', 'Aleksandra Bosacka'] | [] | ['customfield', 'forge', 'javascript', 'trigger'] | 68 |
10,045 | https://devpost.com/software/jira-support-facade | Vote section
Add support request form
My requests
Settings page
Support Facade tab for Issue page
Instant notifications about answers to your requests
Brief notifications for open widget
Instant reload for Request page in widget
Support Facade tab with url, screenshot, console.log, details about user and smartlook.com recordings URL
Sample recording in smartlook.com
Inspiration
One of the nightmares for any developer is support request like "Save form doesn't work!".
I mean, what form are you talking about - whats url of that form? What do you mean by "doesn't work" - is it not saved OR did you get some error? If you got error - is it client side OR server side? If its client side - what did you do in order to get that error? If that's server side - what's your login, so I can check logs? When did you get that error?
Its tough to explain importance of context info for support requests to client OR boss. Usually you got answers like "Ugh... sorry, I am on meeting now, cant talk. Can you just fix that form?"
So it would be great to get all context info collected automatically, for example, via widget which is accessible on all pages for logged in users.
Another nightmare - hundreds or even thousands of open issues in backlog. In one of my project I had open issues from 2013 (ugh.. why did I say that?). So it would be great if we will be able to get feedback from our website users - whats important for them?
One more tricky part - organize effective feedback. Users love live chat's, but handling live chat sessions could take enormous amount of time. From the other side it would be nice to be able to discuss some issue with users in "chat mode". In other words - it would be nice to have ability to combine "Issue based support style" with instant messages in some kind of "issues with real-time live chat comments"
What it does
This plugin provide ability to put simple javascript code on any website and got nice widget, which allow to submit requests to Jira - with page url, screenshot, console logs, logged in user details, link to browser session replay on
https://www.smartlook.com
Also user can get details about his previous issues and vote/downvote for some issues.
Jira users can answer to widget user by adding comment with "plugin user metion" (@JiraSupportFacade).
Widget show selected issue comments in real-time using websockets and give widget user ability to comment issue instantly.
Request page is reloaded instantly as well when new comment added, existing comment updated or some comment removed.
How I built it
I used php/symfony for backend and Reactjs for frontend.
Challenges I ran into
Lack of time. I tried to find some time after regular work, but it wasn't an easy task.
Accomplishments that I'm proud of
I actually did it! I have an ideas for couple Jira plugins since 2015, so I am glad, that I finally did first step.
What I learned
"No time" is bad excuse. Keep moving and you will achive your goals.
What's next for Jira Support Facade
ability to view developer's comments from jira and answer them directly from widget
notifications about status changes and new comments
few other skins
support for not logged in users
Demo video
https://youtu.be/eKC0IRtWFRM
= starting from setup (5 mins)
https://www.youtube.com/watch?v=PPIIXa8nRk0&feature=youtu.be
- interaction demo (3 minutes)
Built With
aui
php
react
symfony
Try it out
jira.facade.support
codegeist.facade.support
codegeist2.facade.support | Jira Support Facade | Simple way to interact with Jira for your grandma + "live chat" for issues | ['Andrew Zhilin'] | [] | ['aui', 'php', 'react', 'symfony'] | 69 |
10,045 | https://devpost.com/software/jira-workflow-documentation | Workflow Documentation on Confluence page with all status, transitions and properties
You need to install the app on both, Jira and Confluence. If not installed in Confluence you will see this error message
Jira Admins can start the creation of documentation pages in Confluence and see an overview of all workflows and links to Confluence
Inspiration
If you set up complex Jira workflows, which affect also users who aren't working with Jira that often, they might be opening Jira issues and don't know what to do next. What is expected in each status of the workflow? Who has something to do? What are the conditions to proceed?
As admin who set up the workflow you probably know the answers to those questions. You have the technical background to explain all the conditions, validators or post functions which might exist. But the users don't have that knowledge and they might be asking what to do and why some users do have different options and possibilities in a workflow compared to themselves.
This problem inspired us to provide a simple way to translate technical workflow configuration in Jira to a descriptive process documentation on a Confluence page.
What it does
As described above, Jira workflow documentation is translating technical workflow configuration to process documentation. All rules and elements of a workflow are written automatically to a Confluence page leaving space for additional description or remarks to explain the whole process.
This Confluence page gets automatically created for each Jira workflow and contains a table describing all steps with transitions and their conditions, validators and post functions.
How we built it
We used the Atlassian Connect framework to build the app.
Challenges we ran into
As it is our first Atlassian Cloud app the whole project was a challenge ;-)
In detail we faced the following challenges:
Authentication across Jira and Confluence. Authentication of Jira app to create confluence page
Getting all relevant workflow information from Jira
Create a section in manage apps in Jira to store information on workflow documentation space and pages
Data storage of target Confluence spaces for workflow documentation
Accomplishments that we're proud of
Building an app that works between Jira and Confluence and that stores Jira workflow information on Confluence pages. We are proud to have accomplished to get the relevant information from Jira configuration and to store it in a structured way in Confluence cloud to provide additional value for Jira users.
What we learned
We learned how the Atlassian Connect Framework works, how it can be used to built an app and that everything is possible in Atlassian cloud products that we know from Atlassian server products. That is where we come from and with this project we started to work in a completely new environment. We are proud that we get the app to work also in this new area of application and that we managed almost all challenges we faced during this project.
What's next for Jira Workflow Documentation
We want to get the app to a more sophisticated status to be able to publish it on the Atlassian Marketplace. In order to achieve that we need to improve the storage of data (storage location of Jira workflow documentation in Confluence) and the possibility to efficiently use the app for all interested customers. Intensive testing of different use cases also needs to be done as next step.
Built With
api
atlassian
cloud
confluence
connect
javascript
jira | Jira Workflow Documentation | We want to provide a solution for better documentation of Jira workflows in Confluence. There should be an easy way to translate Jira workflow configuration into Confluence documentation. | ['Jonas Moehringer', 'Ibrahim Farhan'] | [] | ['api', 'atlassian', 'cloud', 'confluence', 'connect', 'javascript', 'jira'] | 70 |
10,045 | https://devpost.com/software/slack-saver | Start the transfer with just a few clicks on the message you want to save.
Give your conversation a title and select the space to create it in
Picking which messages will make it over into Slack
The final result - the content along with other details about the Slack Conversation
Inspiration
Slack is an amazing tool, and if you've ever used it at your company then you know just how much information goes through it: Daily updates, company-wide discussion threads, analysis and critique of work, and regular plain team communication call Slack their home.
Occasionally, a really great conversation comes through.
Maybe it's a detailed answer to an on-boarding question, or an inspiring exchange about the company's vision. These gems shine through at the most unexpected times and they are truly valuable and worthy to be saved and shared.
Because everything is written down in Slack, that makes it easy to share, right?
Wrong. Because Slack serves as a home for so many routine and ordinary conversations, the valuable highlights that stand out from the pack cannot be isolated and shared in an effective way. How many times have you thought to yourself "I answered this question a month ago", and went searching through Slack only to get lost in the myriad of previous messages.
The problem isn't Slack. Slack better serves as a medium of transfer, not as storage.
That's where Confluence comes in. For years we've been using Confluence as the storage and reference place for memos, instructions, articles, blogs, and other types of more-thoughtful and valuable content than just ordinary conversation.
So why not copy a conversation and paste it in Confluence?
Believe it or not, you cannot just copy and paste a conversation from Slack into Confluence with your keyboard and mouse. It brings along people's names, timestamps, face picture, and horrendous formatting that completes ruins the effort of saving the conversation. Even if you could copy + paste a conversation, not all the messages are valuable. Within a 30 message thread, maybe 15 of those are insightful, the rest simple comments that don't deserve to be saved.
That's where Slack Saver comes in.
Slack Saver allows you to
flexibly
select a range of messages that you want to save and seamlessly create a Confluence Article in your selected space, with a title that matches the context of the conversation. It's an incredibly simple yet valuable tool that we are going to use constantly throughout our workday.
How I built it
I used the Node.js ACE SDK/Library along side the Slack Node.js SDK. It took quite a while to figure out all the nuances with the ACE framework but it was very helpful as I did not have to implement the authorization framework.
Challenges I ran into
A lot of time was spent trying to figure out small, indiscoverable issues. I was using the
httpClient
to interact with the Confluence REST API and kept getting
403
forbidden. After hours of looking, I saw that the
httpClient
was an extension of the
requests
library and used the flag
NODE_DEBUG=request
, which after I finally saw some debugging output that helped me understand what the issue was.
Another challenge with Slack is that conversations can happen in so many different places - direct messages, private channels. They can happen in Threads or in regular messages, or a mix of both. So I had to build the system to be flexible enough to handle the variety of use cases so that the tool would actually be usable.
Accomplishments that I'm proud of
We literally use this constantly at work so I am very happy that we built it. It took a lot of work and I'm happy that people at work are using it daily.
What I learned
SDK's are amazing. The ACE library does a lot of heavy lifting for you. Same with the Slack SDKs. Remember to look at the tools underneath the SDk, and that can help you debug issues and move faster.
What's next for Slack Saver
We would love to build this for Microsoft Teams and other workspace chat tools because we are sure the same issues exist with valuable messages being lost. We don't use those platforms but if people would be willing to pay a small subscription fee, we'd be willing to make it.
Built With
ace
aceproject
api
love
node.js
rest
slack
Try it out
github.com | Slack Saver - Transfer your valuable messages to Confluence! | Ever answered a complex question or written down an in-depth concept in Slack and thought, how can I save this? Now with Slack Saver, take the gems you create in Slack and save them in Confluence! | ['Joel Barna'] | [] | ['ace', 'aceproject', 'api', 'love', 'node.js', 'rest', 'slack'] | 71 |
10,045 | https://devpost.com/software/test-project-qphrce | extracting keywords from summary, description, and comments section of new issues for intelligent querying
allowing free-form search for agents to quickly find other issues
built-in paging so agents can navigate without leaving the issue
The Inspiration
This app was inspired by our own support team’s experience in Jira Service Desk. When a customer submits a support ticket, the first thing most agents do is look for relevant knowledge base articles and related previous tickets to tap into the wealth of crucial knowledge stored in these databases — spending on average 10-15 minutes per new active issue on resolved issue searches.
While Jira does a great job of automatically recommending KB articles that may be helpful, it does not provide recommendations for related tickets that have already been answered. When KB articles aren’t available, agents must leave the Jira issue view by navigating away from the ticket or opening a second tab, and begin an often laborious search for related issues. They manually pull salient information out of the new ticket to formulate complex queries, usually through a process of trial and error, until they find the right mix of keywords to identify the most relevant issues. This is inefficient, frustrating, and time-consuming.
Smart Views for Jira Service Desk takes the error-prone, manual work out of the equation to get agents the information they need — faster.
What it does
With this app, the most relevant previous tickets are automatically pulled into the Jira issue view based on an intelligent query that runs in the background. Agents can quickly and easily browse through past issues without leaving their current screen or writing JQL statements to get the right answers for customers.
This app offers in-line pagination for related issues, so agents can go beyond the first 5 results while remaining on the same screen. If they need to modify the search, agents can use the dynamic search field right within the same interface, while the app does the heavy lifting of putting their keywords into JQL syntax in the background. As the support database grows, this app becomes even more valuable for teams, surfacing the most useful answers from an increasingly broad and noisy repository of information.
No more writing tricky JQL queries or losing precious time due to context-switching and trial and error! With Smart Views for JSD, agents can work more efficiently to shorten response time and help more customers.
How it works
Our team created an automated string parser to extract keywords from the summary, description, and comments section of new issues. Then the app formulates a JQL query to search for these identified keywords in other issues in the same project within the Jira database. The issues that have the highest keyword match rate are prioritized at the top of the list. Because this is completely automated and running behind the scenes, agents do not need to determine the relevant keywords or write the queries themselves.
If agents do need to search issues themselves, they can do it right within the same interface. The search is super fast and responsive with results auto-populated as search terms are being typed.
This app requires zero configuration and can be used immediately from the moment it is enabled. No backend server support is required. No queries or code need to be configured. All functionality and search criteria are built into version 1.0.
What’s next for Smart Views
We’re excited to start getting feedback from early adopters. We have a roadmap of ideas to improve the relevancy of recommended issues, integrate with other text engines, and make this app even easier for agents to use, and we look forward to refining that roadmap as users share their experiences with us.
Built With
aui
html5
javascript
jira | Smart Views for Jira Service Desk | Jira Service Desk agents need to find answers to customer requests quickly. The Smart Views app intelligently finds related issues and allows agents to run queries without ever leaving the issue. | ['Holly Wright', 'Eric Olson', 'Jeff Pierce'] | [] | ['aui', 'html5', 'javascript', 'jira'] | 72 |
10,045 | https://devpost.com/software/bitbucket-activity-board | Inspiration
This project was inspired by
https://github.com/abhijeetps/weekly-digest
What it does
The CConfluence macro generates a high level overview of your teams repo and workspaces
How I built it
The project was built using Atlassian Forge toolkit and Bitbucket APIs
Challenges I ran into
I have never written React ccode before, so it took a while to get things running at the bare minimum.
There's also no Bitbucket support in Forge as of now, hence all of the requests had be done through raw API requests.
Accomplishments that I'm proud of
It works!
What I learned
Forge has a great dev loop workflow: {deploy,log,patch,deploy}
What's next for Bitbucket Activity Board
More context for pull requests/builds and commits
New layout
Built With
javascript
node.js
react
Try it out
bitbucket.org | Bitbucket Activity Board | This confluence Macro helps you get a quick overview of your workspace activities on Bitbucket - hence giving you insights on on your Team or open source project progress. | ['Arthur Kennedy Otieno'] | [] | ['javascript', 'node.js', 'react'] | 73 |
10,045 | https://devpost.com/software/forge-customizable-ratings | Rating macro
Fully customizable Rating options
Rating macro configuration settings
JIRA configuration settings
Jira created on successful rating
Content of JIRA created
Inspiration
We wanted to create a easy way to add a rating section to confluence pages. This rating macro lets you do that, and also creates new JIRAs for the responses. The rating text, buttons and other options are completely customizable.
The rating can be done anonymous or with the user name.
What it does
This macro lets the user add a fully-customizable rating section to any part of the confluence page.
Any responses to the rating section are created as a new JIRA (according to the user settings).
The ratings can be made anonymous also.
The rating is a 5 point scale. The text of the Rating button as well the text of the rating scale is customizable from the macro config settings.
This saves a lot of time when asking for product reviews, content reviews etc
How I built it
This was built using Atlassian Forge platform. The code is written using node.js/typescript. It also requires permission to write to JIRA.
Challenges I ran into
Initially setting various states in the rating form was difficult, but a good understand of the forge API helped to fix the issues.
What's next for Forge Customizable Ratings
We want to work on customising the UI of the ratings form, and also launch it for other atlassian cloud products.
Built With
confluence
forge
forgeui
node.js
typescript
Try it out
bitbucket.org
proto-labs.atlassian.net | Forge Customizable Ratings | Forge macro to add a fully customizable rating section to confluence pages. The responses are automatically added to a Project/Jira Board of users choice. Rating can also be anonymous. | ['Anand C', 'Jayshree Anandakumar'] | [] | ['confluence', 'forge', 'forgeui', 'node.js', 'typescript'] | 74 |
10,045 | https://devpost.com/software/similar-issues-ai | Get those hard to find Issues using machine learning.
See matching issues in a Glance. Here "attachments" matches "video uploads" without sharing any actual words.
The idea of seeing "Person" in a "Location" is matched with "Contacts on a Map"
Inspiration
Large projects and teams often struggle with organizing their issues. Sometimes duplicate issues are created, other times it can be hard to locate related issues when different words or terms are used. Traditional search methods can't find matches when different words or vocabulary are used. I wanted to create a simple interface that automatically displayed similar issues based on issue concepts, rather than words.
What it does
Similar Issues AI uses word vectors (embeddings) to calculate how similar two issues are at the conceptual level. Similar issues are presented as an issue Glance, ordered by similarity. Users can include Closed tickets with a simple filter.
How I built it
A Django API communicates with postgresql, elasticsearch, and a word embedding RPC server to facilitate all the connections. Web panels are built in React, proxied through the Django server.
Once the app is installed, all the issues in the account are indexed as vectors into Elasticsearch. When a user views an issue, we fetch similar results by extracting the tokens with the highest
tf-idf
from the input issue, then calculating the cosine distance against all other issues.
Challenges I ran into
Word embeddings work less well when you have to average a vector over many sentences or phrases. Due to limitations in the
dense_vector
and
cosineSimilarity
features in Elasticsearch, it wasn't feasible to construct and search a vector for each sentence or phrase within an issue. Instead, we select the tokens with the highest TF-IDF score from the issue we are searching against, and use that to generate a vector to calculate distances.
I also struggled a bit with Atlaskit components, since many of them are not truly intended to be used externally to Atlassian. I wanted to use SmartCards or would have loved a canonical Issue component, but instead built my own.
I'd also like to create a way to issue the Glance status up to date continuously so users can see up front how many potential similar tickets there are. Currently this is an expensive operation, since every time an issue is added or updated, it could impact the count of every other ticket.
Accomplishments that I'm proud of
The first time I was able to display related tickets that didn't share any words with each other, but that were linked conceptually, was gratifying. I wasn't sure if it would work.
What I learned
I had an opportunity to try about 10 different natural language and word embedding libraries. It was also good to get acquainted with Atlassian's API for future projects.
What's next for Similar Issues AI
I'd like to create a general search page so that users can find issues conceptually rather than using traditional stemming methods. If there's a way to plug into the existing advanced search, that would be preferable. After some more iteration I'd like to make it available on the marketplace.
Built With
atlaskit
atlassian-jwt
django
elasticsearch
fasttext
postgresql
python
react
Try it out
similar-test.mulch.dev | Similar Issues AI | Find similar issues in Jira, powered by machine learning. Issues are matched even when completely different words are used. | ['Alec Koumjian'] | [] | ['atlaskit', 'atlassian-jwt', 'django', 'elasticsearch', 'fasttext', 'postgresql', 'python', 'react'] | 75 |
10,045 | https://devpost.com/software/fashionkart | Inspiration
Fashion Retailers try to draw inspiration from external sources such as e-commerce portals and online fashion magazines to design the next set of fashion products that they can launch in order to delight the customer. However, it is a manual effort-intensive process, requiring a large team of fashion designers. In order to reduce dependency and make the overall process more efficient, the Retailer wants a scalable tech solution to extract winning designs of apparels and footwear in a consumable format so that the same can be incorporated in the upcoming design of fashion products.
Problem Statement A fashion retailer wants to source ongoing and upcoming fashion trends from major online fashion portals and online magazines in a consumable and actionable format so that they are able to effectively and efficiently design an upcoming fashion product portfolio.
What it does
A one-Stop platform for fashion designers which scrapes the internet for the trending fashion websites and presents it in a single and easily consumable format. It is also capable of giving sales recommendations to retailers and tell which designs have a high sale probability using the power of convolutional neural networks. This tool is also smart enough to auto-generate new design patterns from existing ones using a synchronous, interactive, generative, adversarial network. The web sections include the main page where all the sites state who is presented in views. Here you can find the trending designs of the top fashion Web sites on the Internet. The next section is the celebrity section. This section keeps track of the brands endorsed by celebrities and the designs they wear. Retailers can keep track of these designs and implement them in their manufactured products. Next comes the sales recommendation section. This section shows how well a particular design would do in the market. It takes into consideration previous reviews of the customers and the type of designs they're like. Let's talk about the future scope of this platform. One would be the addition of virtual try-on 3D human models to enhance designers experience and improve on designs using augmented reality next to a ladder users administration portal to classify and give access to users and manage their feed based on interests. Panels for marketing team sales teams and design team to virtually collaborate and share designs and inspirations virtually. We would also integrate designing and editing tools in the solution so as to establish it as one-stop for all needs of designers and teams.
How we built it
The project is built over the strong base of Atlassian connect and followed by a backend using scrapy , AI GAN models in the following ways:-
Scrapy to scrape up to date fashion trends from across the internet in form of link and images to the apparel.
Cloud service (FAAS) on Atlassian Connect to enhance the scalability of the product for large scale user group
AI GAN Model to generate new designs from already existing trendy designs.
Powered with CNNs to give sales recommendation to increase sales probability( By using audience and retailer reviews it learns peculiar details from the data)
High CI/CD support as Project built as a confluence macro hence deployment within seconds .
Cross Platform cloud support to ensure maximum reach to users across devices and platforms.
Challenges we ran into
It was a complete thrill-packed experience, getting started with Atlassian cloud products seemed like a difficult step to do, but thanks to the great documentation and video tutorials provide at Atlassian site, made it extremely easy for us to understand the workflow to make cross-platform apps quite easily
Accomplishments that we're proud of
We are proud to build upon technologies which were more or less alienated from us and worked under a short window of time to give life to this idea of ours by building an industry-ready platform from scratch.
What we learned
We learned to use the atlassian connect platform and to integrate scrapy and other such libraries. We also learned about DL model and it's realtime applications.
What's next for FashionKart
Addition of virtual try-on on 3d human models to enhance designers experience and improve on designs and add AR try on features.
Add a users portal to classify and give access to users manage their feed based on interests.
Adding panels for marketing team , Sales teams and design team to virtually collaborate and share designs and inspirations virtually.
Integration of designing and editing tools in the Solution so as to establish it as one stop for all needs of designers and teams.
Built With
atlassian
bootstrap
connect
keras
nodefetch
python
scrapy
tensorflow
Try it out
fashionkart.live | FashionKart | A single point online portal for fashion retailers and designers to draw inspiration from external sources across the internet, to get inspired by recent trends in the fashion industry. | ['Akash Bajpai', 'Chinmoy Chakraborty'] | [] | ['atlassian', 'bootstrap', 'connect', 'keras', 'nodefetch', 'python', 'scrapy', 'tensorflow'] | 76 |
10,045 | https://devpost.com/software/random-splash | Inspiration
As they say -
A picture is worth a thousand words
. When working with documents, most of the time you might want to add pictures to represent a placeholder. Usually, adding a picture just for a placeholder means many additional steps, and many times you have to make do with the same repeated image of standard quality. Bringing, Random Splash to the rescue!
What it does
Random Splash is an app built using Forge for Atlassian Confluence that allows you to add random images from Unsplash in your document. Use it for inspiration or use it as a placeholder - the choice is yours!
How I built it
The main technology utilized for this app is the Forge platform - provided by Atlassian. The programming language utilized is JavaScript. The Unsplash API has been utilized to fetch the random images with the relevant token and the query parameter.
Challenges I ran into
Forge was a new platform to work on - but I am happy to say that the tutorials provided by Atlassian helped a lot to solve most of the challenges faced during the development.
Accomplishments that I'm proud of
This is the first time I have built an app using Forge and I feel I got the hang of it quite quickly! I am also happy that I was able to move ahead despite the technical roadblocks that came in between.
What I learned
I learned the Forge platform for Atlassian’s cloud products and explored the Unsplash API.
What's next for Random Splash
A welcome addition to the app will be the ability to pass the search query while calling the macro. Since Forge is still in beta, this feature does not seem to be currently supported, but once it is, I will surely love to add that!
Built With
confluence
forge
javascript
node.js
Try it out
github.com | Random Splash | Add random images to your Confluence document - powered by Unsplash! | ['Hannan Satopay'] | [] | ['confluence', 'forge', 'javascript', 'node.js'] | 77 |
10,045 | https://devpost.com/software/page-activities | Inspiration
Users who receive a lot of notifications might overlook some of them. These may include important updates to a page that they care about. By adding a centralised notification for all updates that happened to page on the page itself, user will be able to quickly view changes that occur to a page that they might be unaware of.
What it does
Page Activities shows all page updates and new comments that occured since user last viewed the page. This way, user will be able to view all updates to the page in one place and glance through changes that might need their attention.
How I built it
Built using Atlassian Forge framework which enables me to get the app up and running in a breeze.
Challenges I ran into
Forge UI does not allow custom styles or components and limits what can be displayed in the UI. I resorted to redirecting user to an existing version changes or search page instead of displaying them inline because of this limitation.
Unable to use
useContentProperty
hook because
localId
is not available in the functions.
What's next for Page Activities
Track other activities besides page updates and comments, e.g. mentions. | Page Activities | Quickly view activities that occured on a page since your last visit | ['Brigitte L'] | [] | [] | 78 |
10,045 | https://devpost.com/software/manny-4srdcp | Inspiration
I love Trello and use it both personally and professionally. One challenge I've faced is wanting to take action on multiple cards at once, but not necessarily in any particular order.
What it does
Manny lets you select individual cards to bulk move to another board/list, apply labels, or archive.
How I built it
It's built with the Trello API and React.
Challenges I ran into
Certainly understanding boards/lists via the Trello API, and really just ensuring brand guidelines are met for a seamless integrated Trello experience.
Accomplishments that I'm proud of
Manny is currently installed in over 1000 boards!
What I learned
I learned about creating Trello Powerups, the Trello API, and submitting them to the store.
What's next for Manny
Now that bulk labelling and archiving is done, I'll take stock of what other bulk actions are missing from the Trello experience. I'm open to feedback!
Built With
react
trello
Try it out
trello.com | Manny | Gone are the days of applying actions to ALL cards in a Trello list. | ['Alex Sopinka'] | [] | ['react', 'trello'] | 79 |
10,045 | https://devpost.com/software/tldrize | Inspiration
As remote work is becoming a new normal, smooth and effective communication is proving to be one of the major hurdles for the tech-companies today. This problem gets amplified when a developer tries to communicate a technical problem in writings. More often than not, the major point is lost in the translation resulting in the waste of valuable time and frustration among the employees. As a personal experience, onboarding as a new intern was extra challenging due to the lack of proper documentation and a central place to ask general questions. As a solution to overcome these communication barriers, we introduce
PRJ
.
What it does
PRJ provides a central platform for developers to ask questions instantly through the screen, voice, and/or video recordings. The developers can post the video-question within a specific team or company-wide along with an option to tag relevant team members to view/address the issue. Further, before posting the questions, the developers can use a smart search option - uses AI to search for any relevant words mentioned in the video, to search for the previously solved issues.
How we built it
PRJ is a serverless app with a React front-end and serverless backend using AWS Lambda, Amazon API Gateway, and DynamoDB. Further, Atlassian connect was used to integrate Jira with PRJ.
Challenges we ran into
Since we wanted to use create-react-app for easy deployment, setting up Atlassian-connect with create-react-app was the major challenge for us. We eventually found a workaround, thanks to the extremely helpful mentors of Codegeist. This was also our first time creating a serverless app and working with Atlassian products so the learning curve was steep but we learned a lot and enjoyed the process along the way.
Accomplishments that we're proud of
We are proud of coming up with a solution to help millions of developers in this unprecedented time as well as creating and deploying our first-ever serverless app.
What we learned
We learned the serverless framework, integrating Jira using Atlassian connect, creating the serverless backend through Amazon API Gateway and Amazon Lambda and deploying the app on the cloud.
What's next for PRJ
Moving forward, we want to add functionality to link the current code snippet on the video directly to the code repo. This way developers can directly move from the video to the code snippet of interest with just one click which also takes away the guesswork in finding the right lines of code.
Built With
amazon-cloudwatch
amazon-dynamodb
amazon-route-53
amazon-web-services
atlassian-connect
aws-api-gateway
aws-lambda
cognito
grommet
hubcap-api
javascript
node.js
react
serverless-framework | PRJ-2020 | PRJ | ['Smit Rao', 'Aslesha Pokhrel'] | [] | ['amazon-cloudwatch', 'amazon-dynamodb', 'amazon-route-53', 'amazon-web-services', 'atlassian-connect', 'aws-api-gateway', 'aws-lambda', 'cognito', 'grommet', 'hubcap-api', 'javascript', 'node.js', 'react', 'serverless-framework'] | 80 |
10,045 | https://devpost.com/software/ronin-reports | Atlassian Store Quote template
COVID-19 template
Flexbox Layout template
Beer ecommerce template
Confluence Homepage template
Cat Breeds template
Comala Document Control template
Templates Catalog
Report Editor
Inspiration
We believe that our solution tackles two important aspects: i) Data Integration, and ii) Data Presentation.
On the one hand, one of the key features that keeps customers coming to the Atlassian ecosystem is
the tight integration among all the products
e.g., a single Jira issue displays information from Bitbucket, Confluence, Bamboo, Pipelines… But customers still suffer two main friction points, which are still to be overcome when it comes to data integration:
Data coming from marketplace vendor apps
Data coming from vendors outside the marketplace (ERP, CRM, SaaS…)
On the other hand, and after having worked for two vendors of the Atlassian Marketplace (Keinoby and Comalatech), we realized that we’d built different reports for all their apps, and sometimes had to do it several times for the same app. We also created some custom apps for third party organizations, which also needed reports.
So, reports are a commodity in the ecosystem. But currently, these reports fail when customers need the information in an organized format due to the lack of flexibility of the current solutions. There’s no way to present the data adequately for the audience at hand, nor to integrate data.
What it does
Ronin Reports allows users to create reports using tables, graphs, charts, images or plain text to present the information. In addition, this app gives flexibility to design the reports in a flexible and responsive layout structure.
Ronin Reports uses JSON as data source, a static JSON, from a REST API endpoint (public or private), GraphQL endpoints… So it could combine data from Confluence, Jira, Hubspot and your favourite cat API if it’s needed in a single report. Even databases can expose the data through a REST API in JSON format, so we can capitalize on that too. And we also allow user interaction, so the reports present dynamic information.
Keeping it simple: Ronin Reports creates flexible and dynamic reports using JSON data.
How we built it
Using React capabilities and it's tree component model, we created specialised view components, which can be mapped into any part of a JSON structure.
A key part was to provide a powerful data source implementation to smartly gather data in any source (static JSON, a public REST API, a proxied API to solve CORS issues, Confluence using AP.request bridge, and so on) and the puzzle is complete: A markup JSON based definition where users create a powerful, custom and free-layout visualization to display it within Confluence.
Challenges we ran into
While the idea it's simple, we run into multiple challenges (still working on some of them):
Powerful custom reports
. We focused on giving users a powerful tool with a lot of
flexibility
, but that brought
complexity
. The current solution demands users to have basic knowledge of CSS (Flexbox) and JSON path. To reduce this barrier, we provide a catalog of templates. This set of examples cover different use cases that users can copy, tweak and adapt to their needs. We think this can hinder adoption, so we are working to make it as easy as possible.
Dynamic reports
: We didn’t want to provide just a static version of the data, but dynamic reports based on custom parameters. The logic behind it was complex, as we needed to have a fine control on how React controls the rendering. We manage multiple contexts, and this has to be done properly.
Recursivity
: Reports are recursive tree structures. This means that a customer can have a table within a cell table or multiple nested data sources. This provoked several issues due to incorrect nested structures, so we had to delimit where to allow customers to use recursivity.
Isolate the report core
: After implementing the PoC to validate our ideas, we thought we should separate the rendering code. In this way, it can be reused, but this called for an early refactor of the entire project.
Accomplishments that we're proud of
We think we have created a solution flexible enough to solve several of the current reporting problems in the ecosystem, with some opinionated technical decisions:
JSON as data format
HTTP REST as first order data source
Extended JSON path as data mapping solution
CSS Flexbox as basis for the layout design
Custom and specialized view solutions: Text, tables, lists, graphs, etc.
A reusable library that could be the core report engine for other app vendors
With these pieces, a user can offer beautiful, custom and powerful data abstractions to present information in an organized format to the rest of the team.
What we learned
Advanced React skills
Importance of balancing power with complexity when providing features
Overcoming several oddities in REST APIs: Rate limits, CORS, etc.
Advanced features: PDF and image export (WIP)
What's next for Ronin Reports
The main challenge we face is to reduce the complexity when building the reports. We are going to start providing a catalog with several templates covering the main features and possibilities. Next step is to provide small improvements to reduce that complexity: Extract the datasource logic to the configuration area, create a simple layout design builder… A rough outline of our roadmap -which changes everyday 😺:
Short term:
Compose facilities: Allow templates to be broken down into smaller buildable pieces
Configurable query cache
Nested datasource queries
Enhanced authentications: OAuth 2.0
Automated pagination
Improve filtering and parameter support
Multiple UI enhancements (tables, styles, graphs, etc)
Catalog: Add several useful examples and integrations
Middle term:
Report builder: Simplify the report creation and layout design
Provide the functionality as a library for third parties, like other app vendors. So they can use it in their apps and forget about maintaining their own reporting solutions
Improve and create new exporters: PDF, CSV, image, etc.
Catalog: Add custom third party integrations and customer contributions
Long term:
Increase the power of the reports by allowing interaction with the data e.g., POST/PUT actions in endpoints, metadata, etc.
Built With
ace
atlaskit
css
flexbox
graphql
javascript-es6
json
jsonpath
markdown
node.js
react
rest-apis | Ronin Reports | Powerful, flexible and professional reports from any data source. Present dynamic data to improve the communication in your team | ['Gorka Puente', 'Iñigo Gonzalez', 'Javier Coira'] | [] | ['ace', 'atlaskit', 'css', 'flexbox', 'graphql', 'javascript-es6', 'json', 'jsonpath', 'markdown', 'node.js', 'react', 'rest-apis'] | 81 |
10,045 | https://devpost.com/software/bountify-z5e063 | Inspiration
At our company anytime someone goes the extra mile we make it appoint to show our appreciation by either getting them a coffee or buying them a pizza if they work after hours.
We created this app to streamline this culture - anytime you want to challenge or are looking for someone to go the extra mile you offer a bounty on an issue.
What it does
We allow people to set bounty's on issues. So if someone does some obscure task or goes the extra mile - you offer them a good gesture, by default on the app we offer coffee, pizza, a hug, high 5 but this can literally be anything to encourage someone to really look into that issue.
Bounties can range from asking someone to compile a list of countries for you in JSON format for a coffee and the python dev in your company quickly scrapping wikipedia for you to earn that reward - to simply asking someone to figure out why your code isn't running
How I built it
We built the app in Javascript using Forge
Challenges I ran into
We had trouble with Forge tunneling and thus we had to rebuild the app with every change - hectic
Accomplishments that I'm proud of
We were able to put something together
What I learned
A lot about Forge!
What's next for Bountify
Improving the application, fixing small bugs and trying it out with other teams.
Built With
javascript | Bountify | Challenge your team to go the extra mile by adding rewards to resolving issues | [] | [] | ['javascript'] | 82 |
10,045 | https://devpost.com/software/agile-poker-for-jira-cloud | Inspiration
We had relative estimation before - but it was a single person experience. Our customers asked for something that will engage a whole distributed team.
What it does
Our solution allows the whole team to participate in a relative estimation session (based on the Magic Estimation method). People drag issues around, put them to the columns to show what is the estimated size of a Story or a Task. They can see what all the other participants are doing, what are they dragging and where are their cursors (with avatars). All in real time! After everybody is done, save all the estimated values in one click.
How we built it
We already had a functional connect app. We supercharged it with few additional techs (Google cloud platform, esp. firebase) and built the new estimation mode basically from scratch - with storybooks, tests etc.
Challenges we ran into
There were two, one technical, one not so.
The easier one (the technical) was how to make people see their actions in near real time. We ran into multiple race conditions, UI freezes, etc. Finally, with the help of
https://firebase.google.com/docs/database
we managed to make it work well. The second one was harder. How to make the multiplayer experience as effective and fast in estimating as the single player is. We believe we did it, but only the users can tell.
Accomplishments that we're proud of
We are using feature flags, incremental rollouts and we always have the latest version deployed to production.
The cursors location visualisation, no matter if they are in ones viewport or somewhere outside.
Team Relative was estimated using Team Relative!
What we learned
Technical is easy when compared to delivering value. First few attempts we tried were plain not useful. Even for us, people who developed it. We had to change our idea of a multiplayer relative couple of times before we were able to use it for our own estimation sessions.
What's next for Agile Poker for Jira Cloud
We are not finished with multiplayer estimations - next task is to bring the Bucket Sizing to distributed teams.
Built With
connect
firebase
node.js
vue
Try it out
marketplace.atlassian.com | Team Relative estimations for Agile Poker | Estimate large number of stories/issue quickly and as a team! | ['Grzegorz Tańczyk', 'Oleksii Kovalenko', 'Łukasz Matuszewski', 'Michał Nykiel', 'Grzegorz Molicki', 'Adrian Bilicz', 'Bartłomiej Zięba'] | [] | ['connect', 'firebase', 'node.js', 'vue'] | 83 |
10,045 | https://devpost.com/software/bug-search-from-jira | Inspiration
Often for an assigned bug, developers search on StackOverflow on what can be the possible reasons for this bug.
What it does
The app will provide the direct URL to the top 3 StackOverflow link for a given issue based on the JIRA ticket summary. This allows the developers to get links to top results directly in JIRA.
How I built it
Using Forge UI and APIs.
Challenges I ran into
Getting started with Forge.
Accomplishments that I'm proud of
Working app. An app that can save developers' time and focus. It will show the top results directly in JIRA. No context switching to open new tabs and search.
What's next for Bug search from JIRA
Using NLP to understand the entire JIRA ticket better and then search. This will further improve the search results.
Providing a search textbox where users can search for their query and retrieve the result.
Built With
forge
javascript
Try it out
github.com | Bug search from JIRA | The app provides the direct URL to the top 3 StackOverflow link for a given issue. This allows the developers to get links to top results directly in JIRA. | ['Mashrin Srivastava'] | [] | ['forge', 'javascript'] | 84 |
10,045 | https://devpost.com/software/days-left-timer-for-confouence | Inspiration
Ability to display in one place approaching deadlines.
What it does
It display deadlines on confluence page.
How I built it
I build it with forge.
What I learned
Configuration for forge apps.
What's next for Days Left Timer for Confouence
add support for different time-zones
add some graphics to make it look pretty
Built With
forge | Days Left Timer for Confluence | Add days left for approaching deadlines to confluence page. | [] | [] | ['forge'] | 85 |
10,045 | https://devpost.com/software/friendly-sms | Inspiration
There are various ways to message your friends. As a beginner in Typescript (as I was not used to with javascript), i decided to make this service so that i can have some experience in it. And making end to end solution with Forge made me to work on this project.
What it does
Its simple. Write message and your mobile number and press “Send”. Your friends will receive your message instantly.
How I built it
With Atlassian Forge platform and language used was Typescript. I used ClickSend Api from RapidApi site.
Challenges I ran into
Accomplishments that I'm proud of
What I learned
What's next for Friendly Sms
Built With
atlassianforge
clicksend(api)
typescript
Try it out
awesome-sam.atlassian.net | Friendly Sms | Message instantly to your friends. | ['Sam J'] | [] | ['atlassianforge', 'clicksend(api)', 'typescript'] | 86 |
10,045 | https://devpost.com/software/replio-for-jira | Inspiration
As smartworkers we love our freedom. And it's freedom that we drew our inspiration from. Being Jira users, there were two key issues that bothered us. Firstly, accessing Jira from non-PC devices wasn’t always practical. Secondly, having to leave the current platform to check our tasks was frustrating. This is what prompted us to develop a chatbot that could be integrated in different environments and easily accessed at any time from any place. From that, we got carried away and felt that we could add more value to Replio by helping Agile and Atlassian newbies master the key concepts.
What it does
Replio is an AI-powered multi-platform chatbot which makes it easy to quickly access your Jira information, log your work, comment your tasks and assign them to your collaborators from any device. It saves you the inconvenience of opening Jira every time you need to perform an action as well as the frustration when you access it via non-PC devices. Replio can also be of great help to those who work within the Agile framework but are not Agile gurus. Replio answers questions such as “Define scrum”, “What is meant by definition of done?” or “Who are personas?”. It also knows a lot about the Atlassian products and can dispel all your doubts. The strength of Replio is that it understands natural language so there’s no need to learn fixed commands or phrases. Based on machine learning, it keeps learning every day. And it gets better. Replio is a real dynamic virtual assistant.
How we built it
Replio was built on AI and NLP resources. We created two knowledge bases, one for Agile concepts, the other for the Atlassian products. The technologies that were exploited are Atlassian Connect, Nodejs (backend). Deploy is based on Heroku and Google Cloud Platform.
Challenges we ran into
Developing multi-platform software is always a challenge. Every platform has its own specific features so we had a bit of a hard time standardizing user experience.
Accomplishments that we're proud of
We are proud to have taught Replio to perform a diversified range of tasks. Despite having very little time, we created an assistant that does what it’s supposed to and can converse naturally with the users. We are happy to have stood by our values of freedom and agility and to share them with Replio users.
What we learned
Having always used Scrum, for this plugin we decided to turn to Kanban, which was entirely new to us. Also, we improved our Slack knowledge.
What's next for Replio for Jira
Our short-term aim is to expand the range of functionalities that can be performed through Replio. Our final goal is for Replio to be able to interact with all the Atlassian products. We view Replio for Jira as the first of many Replio skills. We are working towards the development of the skills Replio for Confluence, Replio for Service Desk and Replio for Bitbucket.
Built With
atlassian-connect
express.js
google-cloud
javascript
machine-learning
node.js
react
slack
teams
Try it out
presago.net | Replio for Jira | An AI-Powered virtual assistant for Jira. You choose your favourite platform and device, Replio does the rest. | ['Alessandro Distefano', 'Barbara Berti', 'Andrea Arcifa', 'Giovanni Palmeri'] | [] | ['atlassian-connect', 'express.js', 'google-cloud', 'javascript', 'machine-learning', 'node.js', 'react', 'slack', 'teams'] | 87 |
10,045 | https://devpost.com/software/classic-settings-for-next-gen-jira-projects | Classic Settings
Helping users and organizations with the transition to Next-Gen projects on Jira Cloud
Inspiration
It started with our own need. We were just starting our new Jira instance with next-gen Software and Service-Desk projects, and soon missed some settings. While searching for solutions, we noticed a lot of users are looking for the same features. This lead to the community and it's leaders being very active on the subject, and a lot of effort by the Atlassian support team, which also inspired how we give support ourselves. The more we got into this subject, the more we realized this shouldn't be an issue blocking organizations from moving to next-gen projects.
All of this made us start to think about the app and if it can bring more value in the future, and that question got answered fast as we soon got to know AtlasKit and components like the user picker and the new awesome text editor. Combining this with existing API support meant we can actually give users a tool that is in Atlassian quality and really helps feel at home for new next-gen project administrators.
What it does
Next-Gen projects are different and not all the project settings fit in. That said, some missing settings from classic projects apparently can really fit well into next-gen, but yet are missing. Classic Settings brings them back...
Projects lead
Default assignee
Project URL
Project description
Everything functions exactly like it used to in classic projects, and all the effects on the system are the same. The only little bit we added is the new Atlassian Design look and feel, and giving the description fields more respect, hoping more more users will appreciate it.
How we built it
This of course started as a script that we used every time we needed, but when it was go time, there was no doubt. On the frontend, AtlasKit is here for us, and we're utilizing it to the fullest. On the backend, we turned to our trusted existing AWS infrastructure, and we only use Atlassian APIs to get the right results. And of course... Everything comes to life with Atlassian Connect framework.
Challenges we ran into
One might think we just copy pasted feature from classic projects, but this is not the case at all. Classic projects and next-gen have some inherent differences, and porting the fields was not that straight forward. Having to go over all of the different classic projects for testing, really makes you appreciate next-gen.
Accomplishments that we're proud of
The product is reaching 250 users in just a few months, and the reviews and community support really are amazing. There is nothing better than knowing you are really helping. We're also proud of how we changed some classic features just a bit to find the middle ground between being a familiar comfort and a gateway to the new and better. Every time we look at the menu entry "Classic settings" above "Project automation" it feel so natural.
To name a few more technical accomplishments:
Getting on top of how to properly port permissions and other details from classic projects to next-gen.
The new text editor from AtlasKit was a must for us, and integrating such a huge component is never trivial.
What we learned
Classic Settings is a different kind of product and so were the lessons we learned. We learned a lot on what it means to be a member of the Atlassian community, and the big efforts support teams invest. But the biggest take is how good it feels to just help the community. All the feedback really pushed us into giving the product more thought, making it a true help for the transition to next-gen.
Not your classic lessons learned ;)
What's next for Classic Settings
Keep on helping and find new ways to do so!
Like a lot of other developers, we are waiting for related APIs to mature so we can support more project settings. This will enable a whole new set of features to be made available for our users. But we're not stopping there. We're also exploring more elaborate ways of assisting with the transition to next-gen. Some outside of the project settings. And last but not least, we're very exited to see how our users use the new text editor and already have big plans for it.
A word from the author
Big thanks to all of our supporters out there in the Atlassian community! 💙
Built With
amazon-web-services
atlaskit
atlassian
atlassian-connect
bitbucket
css
html
javascript
jira
react
Try it out
marketplace.atlassian.com | Classic Settings for Next-Gen projects in Jira Cloud | Easing the transition to Next-Gen projects by solving a prominent user paint-point: enabling "classic" project settings (setting project description, and changing project lead and default assignee). | ['Addown Studio'] | [] | ['amazon-web-services', 'atlaskit', 'atlassian', 'atlassian-connect', 'bitbucket', 'css', 'html', 'javascript', 'jira', 'react'] | 88 |
10,045 | https://devpost.com/software/forge-insert-image | Insert images using unsplash API
Macro config settings
Enter search term and size of image
Search any image
Inspiration
We wanted a easy way to search and insert images in our confluence pages. Unsplash is one of the leading providers of good quality free and open source images. We wanted a way to integerate Usplash into Atlassian products.
This saves time for users who want to insert related images into their Atlassian workspaces.
What it does
It lets user search images using a keyword and then insert it in the confluence page. Images are fetched using unsplash API. Also, user can select different sizes of images (small/medium/large/regular) using the macro configuration settings.
How I built it
We built it using Atlassian Forge platform. We have used forge API and UI components. The code is written using node/typescript.
What's next for Forge Insert Image
We plan to integerate multiple Image APIs like pexels etc and also let user search and select images using a separate modal dialog.
Built With
confluence
forge
forgeui
node.js
pexels
typescript
Try it out
bitbucket.org
proto-labs.atlassian.net | Forge Insert Image | Search and insert images easily in Confluence. It uses Unsplash API to search free and open source images using the given search term. Option to select different size of images is also available. | ['Anand C', 'Jayshree Anandakumar'] | [] | ['confluence', 'forge', 'forgeui', 'node.js', 'pexels', 'typescript'] | 89 |
10,045 | https://devpost.com/software/pager-0t9364 | Step 1 - Trigger the plugin
Step 2 - Configure the plugin
Step 3 - Confluence page created
Inspiration
We generally create Jira issues from Confluence pages. But we sometimes need to work just the opposite way. We need a simple yet effective tool to create Confluence pages from Jira issues. The Confluence page created using this plugin contains a Page Properties macro and the properties' values will be populated according to the fields of the Jira issue that triggered this tool. We want that (in the near future) that the user could easily customize the page format without using any other tool than Jira or Confluence.
What it does
The plugin creates a confluence page and insert a Page Properties macro and fill the respective table according to the fields of the Jira issue.
How we built it
We built it with the brand-new Forge.
Challenges we ran into
First of all, we weren’t use to Node.js, React; we come from Java, PHP, C/C++ and .NET. We had very limited time. So even the simplest things were difficult to us at first. But anyway, we decided to experiment the new Forge tools instead of the Connect tools that are a lot of mature.
The Forge documentation is getting better each day; but we couldn’t find our way for a couple of questions; and those questions made things difficult for us.
The debugging part was a little bit too dark (limited) to us. We used mainly Forge Tunnel responses, Console.log commands, etc. Maybe we missed an important debugging tool and that’s why we think this way.
Accomplishments that we're proud of
First of all, we are proud of that we met Forge. We discovered how to use Forge and Confluence Cloud REST API and Jira Cloud REST API.
We’re also proud that we learned a lot of things in a very limited time about the tools needed to build and app with Forge that we didn’t use at all such as: npm, Node.js, React, etc.
We were able to submit an app to this contest.
What we learned
We learned:
How to configure our tools (OS, IDE, Repository, npm, Docker, Forge account, instance, etc.)
Which tools that we need to master for developing Forge apps
About the resources available on the web (documentations about Forge, Jira Cloud REST API, Confluence Cloud REST API, React, Node.js, etc.) that we'll need later.
How to achieve some basic interaction between Jira Cloud and Confluence Cloud.
What's next for Create Confluence Page
As a user, I can select unlimited number of fields and custom fields visible on the issue screen; so, I can import the page properties macro more easily. Background: At the moment, the user can only select up to 3 custom fields to be included on the Confluence page that will be generated.
At the moment, the configuration panel lists all of the fields on the system. We’ll show only the fields included on the issue screen.
As a user, I can easily select the parent page of the page that will be created. Background: At the moment, it’s possible to select the space but not the parent page.
As a user, I can easily see whether the page on Confluence needs to be updated (because the Jira issue triggered this page had a modification); so, I don’t have to track the changes on the Jira issue.
As a user, I can update automatically the Confluence page easily by using a button “Update this page” on this Confluence page; so, I don’t have to manually update the Confluence page according to the changes made on the Jira issue.
As a user, I can set the default configuration for the plugin; so, I don't have to configure the plugin (space, fields to include in the page properties, etc.) every time I create a confluence page.
As a user, I can set Confluence templates that will be used when creating Confluence pages; so, I can easily customize the page created using this plugin without the need of any other tool than Jira and Confluence. At the moment, the page created contains only a page properties macro and cannot be customized before the creation.
Bug tracking
Built With
forge
Try it out
bitbucket.org
codegeist-em.atlassian.net | Create Confluence Page | Create a confluence page with a page properties macro filled by a Jira issue's fields | ['Mert YILMAZ'] | [] | ['forge'] | 90 |
10,045 | https://devpost.com/software/read-time-confluence-byline-item | Inspiration
It's nice to see how long articles will take to read when looking at blogs/news so it gives you a chance to bookmark for later, or read now if you have the allotted time.
What it does
ReadTime shows the estimated read time for a Confluence page, in the top byline bar, alongside analytics and last updated date.
How I built it
I used the Forge framework to create the macro.
Challenges I ran into
The Forge framework is very new and in beta, so you're still extremely limited on things like styling/alignment etc. This severely hinders any complexity/customization.
Built With
atlassian
confluence
forge
javascript
react
Try it out
bitbucket.org | Read Time - Confluence Byline Item | Add the estimated time to read a Confluence page to the byline area. | ['Alex Sopinka'] | [] | ['atlassian', 'confluence', 'forge', 'javascript', 'react'] | 91 |
10,045 | https://devpost.com/software/weather-confluence-slash-command | Inspiration
I knew Confluence slash commands would be the new way to easily author rich content, and wanted to incorporate some widgets for people to add.
What it does
The slash command/macro will add the current weather for any desired city into the Confluence page.
How I built it
I used the Forge framework to create the macro.
Challenges I ran into
The Forge framework is very new and in beta, so you're still extremely limited on things like styling/alignment etc. This severely hinders any complexity/customization.
What's next for Weather - Confluence Slash Command
As the Forge framework evolves, I hope to add some more styling and enhance the widget with more information like 7 day forecasts.
Built With
atlassian
confluence
forge
javascript
react
Try it out
bitbucket.org | Weather - Confluence Slash Command | Add the weather for a given city into your Confluence page. | ['Alex Sopinka'] | [] | ['atlassian', 'confluence', 'forge', 'javascript', 'react'] | 92 |
10,045 | https://devpost.com/software/soulwork | The dashboard shows an aggregated summary of all your work in Jira.
Insights give you updates about information and events you care about and interpret what is causing them.
Artificial intelligence predicts outcomes of sprints and epics, identifies atypical time in status, and forecasts delivery tempo.
Spend less time reporting status. Efficiently build professional status dashboards, metrics, and visuals.
Visualize your data and workflows with interactive charts and graphs.
Get into the details. Understand and explain the details behind execution with data, metrics, and trends.
Visualize your issue history in detail with our advanced timeline. Get additional details and see a unified timeline of events.
Reach a new level of performance. Grow and scale good practices across your team.
Inspiration
Building software is one of the greatest professional challenges a person can face. Doing it successfully is rare and full of obstacles. It's incredibly impactful and rewarding when done well.
Anyone who has led a software project has experienced a wide range of emotions: joy and frustration, pride and disappointment, confidence and fear.
Let's face it, leading a software project is
hard
. There is too much activity happening too quickly. Our projects are big, fast, and overwhelming. We can't possibly keep up. So, we blame our tools, our culture–or worse, the people we work with.
There are so many great tools for
building
software. Let's give leaders and managers world class technology for
managing
software projects.
The knowledge, information, and data we need to be successful is there for us–it's in the tools our teams use every day. But we're not able to access its full potential.
We need to put it all together. We need it summarized and to the point. And we need it to adjust on the fly, because nothing ever goes as planned.
With the right technology, we all can be the leaders we want to be. The leaders our teams and companies deserve. That's Soulwork.
What it does
Soulwork gives you the status of your software projects in one place. It analyzes your project data and tells you the story about how you're executing–good or bad. It centralizes data from Jira and organizes it into information your teams can use to make decisions about how to execute.
The story starts with a dashboard–all of the most important activities and information about your projects. It summarizes your most important metrics and trends. It gives you a prioritized and interpretive list of insights: real-time updates that hit you like news headlines. It also highlights your most active epics, sprints, and issues.
From the dashboard, you can dive into the details about the status of your work. See status across your entire portfolio of projects, boards, epics, and sprints. Or, look closely at a single issue. The product tells you the whole story with written and visual communication. You'll see everything that matters to you: completion, defects, scope, workflows, and more.
Dashboards and status details are always kept up to date for you as your project moves along. You can spend less time reporting status and more time taking action. You'll see your work in a whole new way.
How I built it
We used multiple frameworks and libraries to build the product. Our goal was to quickly build a reliable, highly interactive, data-driven web application on top of Jira's API.
The front end web application uses React and JavaScript. State and API data are cached in the browser using Redux. Charts are built with the ReCharts charting library.
The back end platform is built with Django. Django REST Framework (DRF) is used to provide multiple REST API endpoints called by the front end web application.
We built analytics to provide users with impactful, real-time metrics that provide a quick overview of sprint, epic, board, project, and portfolio status.
We implemented artificial intelligence for predicting delivery outcomes and detecting anomalies. We've also developed algorithms to generate insights and prioritize, filter, and organize data.
The Jira integration is built to support both Atlassian Connect and OAuth2 for authorization to customer data. Data is stored in a Postgres database. The application and database are hosted on Amazon Web Services (AWS).
Challenges I ran into
When building the product and through discussions with customers, we learned that:
There is a lot of data in dev tools. Leaders and managers get overwhelmed using this data to make planning and execution decisions.
Charts alone are difficult to understand–especially advanced agile charts. Interpretation with both written and visual communication is most effective.
Developers want to focus on delivery without interruptions for meetings or status updates. They will diligently use and maintain Jira if leaders and managers can get the information they need from it.
Accomplishments that I'm proud of
We applied years of our combined management education, training, and experience to build a product.
We learned from past mistakes and built smaller batches of code that were released more frequently. We made progress faster.
Other companies are using our product to help their own teams deliver better and be more successful.
What I learned
We learned the Jira REST API in detail while building the product. This understanding helped us translate the data into the best possible information for leaders, managers, and their teams.
We increased our knowledge of data science and artificial intelligence and applied it to a problem domain we care deeply about.
We advanced our understanding of agile and DevOps significantly. We've taken the best of what we've learned and developed features that help others build better behaviors and processes for their own teams.
What's next for Soulwork
New Insights, Charts, and Recommendations
Adding insights and charts gives teams the ability to learn more about their processes, what they're doing well, and where they can improve. We're planning to take this further by giving teams new ways to act on recommendations provided by our insights.
Additional Integrations
We're building integrations for additional tools throughout the delivery pipeline. Teams get better information when combining data from Jira with other integrations like Bitbucket, Bamboo, Confluence, and more.
Jira UI Integration with Atlaskit
We plan to integrate more deeply with Jira's user interface using native Atlaskit components. Natively adding our platform's text and visual insights to Jira is a better experience for users. They're able get the information our platform provides without leaving Jira.
Built With
amazon-web-services
connect
django
django-rest-framework
jira
pandas
postgresql
react
recharts
redux
Try it out
www.dosoulwork.com | Soulwork | Make efficient planning and execution decisions for projects managed in Jira. Get unified, focused, and insightful status on your work from the tools you already use. | ['Gautam Muralidharan', 'Cole Grolmus'] | [] | ['amazon-web-services', 'connect', 'django', 'django-rest-framework', 'jira', 'pandas', 'postgresql', 'react', 'recharts', 'redux'] | 93 |
10,045 | https://devpost.com/software/atlas-video-solutions-for-confluence-cloud | Use the 'Video' macro to share the uploaded video
Easy use upload form
Macro edit form
View analytics by user
Rendered Player Overlay
Inspiration
We watch videos every day, whether at home or in our workplace. These days, we are even sharing more videos at work, such as online meeting recordings, training videos, and courses, as more teams switch to remote work options.
There are different ways for sharing videos online. Within your workplace though, it might not be suitable to put work-related videos on Youtube, and using 3rd party apps would still present an issue on how you can embed such videos in your company's Confluence instance.
So, the easiest solution would be to create a page on Confluence and attach the video and call it a day, right?
But what if there's an easy solution embedded in your workplace Confluence instance that lets you upload a video easily, invite others to watch it, and get detailed engagement analytics up to every second from the people who watched your videos. And it's all inside Confluence.
And what if you are a content creator and you want to create videos that have high value, but you are worried that someone can easily download them and share them externally? Well, you can also easily use Digital Rights Management Technologies (it's what Hollywood uses) to encrypt the video, and only the allowed player will be able to decrypt it and play it back.
Atlas+ is designed to simplify delivering videos-on-demand and give you all the options you require to upload, share, and analyze videos within your Confluence Spaces.
What it does
Atlas+ delivers a solution for uploading and streaming videos within your Confluence Cloud instance.
Easy video upload in any Space. The app accepts (.mp4, .mov) video formats and will convert them to MPEG-DASH format for streaming stored in an S3 bucket.
Embed the video using a macro on any page. The macro renders our video player that can play the video stream.
Invite others to watch the video.
Detailed Analytics on your video statistics, including watch rate, completion rate, and engagement. Know which parts of the video most people watched or skipped.
Optionally protect the video with Digital Rights Management (DRM) technologies that will protect this video from being played elsewhere.
Optionally generate auto subtitles for your videos. Currently, the auto subtitle feature supports only the English language.
[Extra Info] What is Digital Rights Management (DRM)?
Digital Rights Management (DRM) is a digital license system that allows content creators control who can use their content, and how they can use it. When a video is uploaded, it is encrypted with a media key, then if a user wants to watch this video, the system authenticates the user and then decides whether to provide a digital license to allow video playback. It's similar to what Netflix and Spotify utilize to protect their content and issue licenses only to subscribed users. With Atlas+, for example, your uploaded video will be encrypted and will only be allowed to playback on our video player that is integrated on your confluence page. Downloading the video using any stream capture extension, for example, will not work as other players can't request a license token to decrypt the video file.
How we built it
The app backend is a NodeJS app, and the frontend is built in React, but it also extends to different AWS services.
After a video is uploaded, we use AWS Mediaconvert to run the encoding jobs, and we store the output in S3 buckets. For Digital Rights Management, Mediaconvert will also encode the video after requesting an encryption license from a third-party provider that we've integrated with as our proxy for DRM licenses (for Widevine and PlayReady licenses). For subtitle generation, we use AWS Transcribe to generate text from the audio file, and then we convert the output to a suitable subtitle file using a serverless function.
The video player is built with the open-source Shaka Player, and we utilize websockets to capture the video events. We've built our own event management system for the analytics, and we calculate the data to create the charts and metrics.
Challenges we ran into
For DRM protected videos, we ran into the challenge of allowing the player to play within the same tab of the Confluence page. Since connect apps are rendered within an iframe, the iframe policy set by Confluence didn't allow access to encrypted-media. To mitigate this, we created an external player and we allowed the macro to open a new tab using the same JWT token generated by confluence to identify the user session and create the analytics.
I believe if this app goes to production, we would see if Atlassian can lift the iframe policy limitation.
Accomplishments that we are proud of
We are proud of the accomplishment of managing to integrate all these small components such as uploader, converter, DRM encoder, analytics into a full breathing app that provides unique value to Confluence cloud in terms of Digital Rights Management and built-in analytics dashboard. We are proud that we managed to do it. :)
What we learned
We are both software developers so there was a huge learning opportunity for us in understanding part of the domain of video engineering and the inner workings of what streaming media companies build, and how Digital Rights Management work. There was a ton of new terminology to know and understand, and there's still a lot. This project has been a huge learning opportunity.
What's next for Atlas+: Video Solutions For Confluence Cloud
This app is a prototype and was just built a week ago for this hackathon. We are going to look into ways to have this running on production soon.
To make it an all-round production-ready app, there's still some work to be done in ensuring full browser compatibility for the player especially for DRM protected videos. We've only integrated for Widevine licenses (which work on Chrome/Firefox) but we still need to request resources to have it integrated with Apple devices/browsers.
In terms of features, we've explored (even spiked some of them) some of the features that will be included in a potential version 1.0 of this app and they include:
Organize the videos in playlists (or courses), and view analytics on the whole playlist.
Add watermark to videos.
Allow users to upload their own subtitles or edit the auto generated subtitles.
Allow users to add jump marks on their videos.
Extend the app to support Jira too.
Built With
amazon-web-services
atlassian
drm
mediaconvert
node.js
react
transcribe
websockets | Atlas+: Video Solutions For Confluence Cloud | Zero config, easy start to upload & create DRM (Digital Rights Management) protected videos. View detailed analytics for your videos and get different stats including user engagement for every second. | ['Abdullah T', 'Ahmed Al-Aghbari'] | [] | ['amazon-web-services', 'atlassian', 'drm', 'mediaconvert', 'node.js', 'react', 'transcribe', 'websockets'] | 94 |
10,045 | https://devpost.com/software/jira-joke-bot | Inspiration
Working for long hours and solving bugs can be tiring. Developers deserve a much-needed break and some laughter in the middle of their work and bug fixes.
What it does
This project contains a Forge app that displays a random non-racist, non-sexist, non-political, non-NSFW, and non-religious "Programming jokes" to the developers. The app will show an UNLIMITED number of jokes for free!
How I built it
Using Forge UI and APIs.
Challenges I ran into
Getting started with Forge.
Accomplishments that I'm proud of
Working app. Something I would myself love using!
What I learned
Forge.
What's next for JIRA joke bot
Non-textual jokes (Memes, GIFs, etc.)
Built With
forge
javascript
Try it out
github.com | JIRA joke bot | The app shows a random non-racist, non-sexist, non-political, non-NSFW & non-religious "Programming jokes" to the developers and gives them a few well-deserved laughs in the middle of their work. | ['Mashrin Srivastava'] | [] | ['forge', 'javascript'] | 95 |
10,045 | https://devpost.com/software/forge-jira-chart | Inspiration
Many a times issues with visibility especially with product managers against software developers is always a common thing. Whereby a developer is allocated a task and the issue takes longer than expected, maybe they encounter blockers along the way or even the Epic was too big and they were optimistic about the issues without subdividing them into smaller pieces. Here is how Jira Charts Come in to clearly show when developers get blockers along the way and transparency about the flow of work being done.
What it does
Shows a graphical presentation of jira issues on a chart and this clearly shows the progress of various tasks
How I built it
Used Forge create to create the Jira project, forge deploy to deploy and finally forge install to install the app, linked the project with the forge Confluence project then added the Jira Charts Macro.
Challenges I ran into
Not being able to integrate with other Atlassian Apps like Opsginie easily since forge only runs on Jira and Confluence.
Accomplishments that I'm proud of
Being able to make the project up and running on the dot net site is a great achievement for me since it was my first time using Atlassian Cloud product
What I learned
Forge helps in improving UI of various Atlassian cloud products and can be customized to suit different user satisfaction
What's next for Forge Jira Chart
Work towards integrations with other Atlassian apps using API calls
Built With
javascript
jsp
Try it out
github.com | Forge Jira Chart | Issues with visibility especially with product managers against software developers is always a common thing. Here is how Jira Charts Come in to clearly show when developers get blockers along the way | ['Maureen Josephine'] | [] | ['javascript', 'jsp'] | 96 |
10,045 | https://devpost.com/software/text2image-xiczl8 | Inspiration
I wanted to create an application where you can share a JIRA ticket retaining the formatting that you probably spent a lot of time doing.
What it does
It converts the text in the description into an image which can then be shared.
How I built it
Forge. JIRA.
Challenges I ran into
Learning the new framework.
What's next for Text2Image
Better parsing and generation for more usecases. Same application for Confluence.
Built With
forge
jira
Try it out
github.com | Text2Image | Are you tired of copying descriptions of JIRA tickets and finding the formatting all messed up?? Worry no more. This app will convert your description into a neat image that you can share! | ['Maansi Srivastava'] | [] | ['forge', 'jira'] | 97 |
10,045 | https://devpost.com/software/prepare-sprint-retrospective | App Settings - only for Jira Administrators
Collected Feedback - only visible to the defined Scrum Master via App Settings page
Give Feedback - all Team members can give their feedback on the active and the last two closed sprints
Inspiration
Every team member knows it: Badly prepared sprint retrospectives!
We both have been working in agile software projects for several years and experience sprint retrospectives without real added value.
Most of the time the Sprint Retrospectives do not add any value because the Sprint Retrospective is not well prepared by the Scrum Master or the team members do not share enough good experiences about the past Sprint.
Therefore we have created the Jira Cloud App Prepare Sprint Retrospective! The app helps the team members to share their Sprint Highlight, Sprint Pain and their general feeling about the current or past Sprint. The Scrum Master gets the overall feeling from the team to the sprint as well as the individual impersonal sprint highlights and sprint paints aggregated. So he already has a lot of suitable input for the Sprint Retrospective without much effort.
What it does
The App Prepare Sprint Retrospective collects the following information from participating team members from one Jira project per sprint: Your biggest Sprint Highlight, your biggest Sprint Pain and your overall feeling about the current or past Sprint.
The defined Scrum Master per Jira Project has the possibility to evaluate the collected Sprint Feedback per Sprint and prepare the Sprint Retrospective with this information.
How we built it
We created a Jira Cloud App as Atlassian-Connect App, the Atlaskit and React. The app is completely serverless, i.e. the app is hosted on netlify and persists all information via Properties API.
Challenges we ran into
The biggest challenges were to define the scope for the MVP and not to get lost in detail during implementation. Additionally we had to get to know React and the components of the AtlasKit.
Accomplishments that we're proud of
We are proud to have built a running and usable MVP in a few weeks, which adds value to the Scrum team within the context of Jira.
What we learned
We learned that the Atlassian ecosystem supports the developer very well. Especially the Atlassian developer community is very helpful. In addition, we learned that scoping is a critical success factor of a software project.
What's next for Prepare Sprint Retrospective
Next we would like to offer the app as beta in the Atlassian App Store and find as many early adopters as possible, who will hopefully give us a lot of feedback where we can improve or extend the app to support the preparation of future Sprint Retrospectives as much as possible.
Built With
atlaskit
atlassian-connect
netlify
react | Prepare Sprint Retrospective | Prepare Sprint Retrospective - Really understand your Team and improve your next Sprint Retrospective | ['Pascal Meier', 'Patrick Roos'] | [] | ['atlaskit', 'atlassian-connect', 'netlify', 'react'] | 98 |
10,045 | https://devpost.com/software/comala-read-confirmations-for-confluence-cloud | Apply the Comala Read Confirmations app to make sure the right people have read the right Confluence Cloud documents.
Using a simple on-page macro, assign users to confirm that they have read content.
When a team member is assigned, they will receive an email alert, letting them know a Confluence page is awaiting their acknowledgement.
Read Confirmations are used by teams for several reasons: signing HR policy documents, onboarding team members or communicating requirements
Team members acknowledge reading pages with Comala Read Confirmations by simply pressing the "Confirm" button.
When content changes in a Confluence page, assign member can re-confirm their read acknowledge so their team knows they have read the page.
With Read Confirmations teams can easily view who has read acknowledge pages they have been assigned and also the version the have confirmed
Inspiration
Our users already enjoy Read Confirmations in our Comala Document Management Family of Apps. Comalatech itself has been using Read Confirmation internally as we have been implementing SOC 2 practices. The feature has proven so useful that we wanted to bring it to Confluence Cloud as a stand-alone app. Making it accessible for teams of any size that are leveraging cloud in their organizations and ready to be installed through the Atlassian Marketplace.
What it does
Assign team members to read Confluence pages, and keep track of who has read them, with Comala Read Confirmations.
Users confirm reading with a simple click, and you can request new people to read the document at any time. If the content of the page changes, send out a new request for confirmation from the previous assignees.
How we built it
Read Confirmations exists as a feature within our existing apps, but there was plenty of work needed to bring it to the Cloud. When Codegeist 2020 was announced, our team kicked into high gear to deliver this app on both the Forge and Connect platforms. The main reason we built our app on the Connect platform is that we wanted this solution to be available after the hackathon is finished, we know that this will deliver value to teams and individuals that need to assign readers to their content in Confluence.
We used the ActionMenu to enable the entry point for our app and we also discussed having the entry point through the Custom Content API in the Confluence page byline-ui, the app will be invoked through a Macro. We made a simple UI for with ModalDialogs that enable the user to choose the Confluence users through the user API, so we can get their profile information and show it to the user to select the readers for the Confluence page.
It is crucial that users get notifications when they have been assign as a document reader, so we built a simple notification service in the backend that enables notifications to be scheduled using the Confluence REST API.
Challenges we ran into
Even though we have read confirmations built into our server products, it didn't mean it was a snap to bring it to the Cloud. The existing feature was integrated right into our approval workflow engine, so our initial challenge was building it out to function independently.
We had an ambitious roadmap for the Connect app and had to make some compromises a long the way to deliver product value from the app, so expect some interesting features when the hackathon ends.
Connect is a very solid and tried platform, our previous experience developing apps in Cloud helped us get everything ready in just a few days. So nothing new on the tech stack, but it is always a great experience to build a new app from scratch and gave us an opportunity to review the recent changes in ACE.
Accomplishments that we're proud of
That our team could create and launch a Connect app in record breaking time, we had to be pragmatic when choosing the features we wanted to build since Connect has a lot of components and modules ready and accesible to developing teams. We choose the one's that delivered a great user experience and enabled important information to be displayed through the Macro.
What we learned
With a small team you need to focus in getting product goals and feature specs ready from day one, so we used Trello to kickstart the project and found that implementing it as a Kanban board is really easy and enables an easy migration of the project to Jira once we have launched it to the public.
Atlaskit lets you deliver an application with their components making it easy to embed into Confluence Cloud, just by following the Atlassian Guidelines. We did not assign a designer to the project and both of this libraries proved to be valuable assets to deliver our app, also it is important for developers to understand that there are different Jira and Confluence assets.
What's next for Comala Read Confirmations for Confluence Cloud
We're not stopping here with Read Confirmations. We have plans to release additional features for the app, and we've also discussed integrating it with our Comala Document Control app. The future should be exiting for both Confluence Cloud and Comala Read Confirmations!
Built With
ace
api
confluence
node.js | Comala Read Confirmations for Confluence Cloud | Comala Read Confirmations allows users to confirm that they have read a key document or page with a simple button. Anyone can request reviews from specific users and track read acknowledgement. | ['Naiara Martín', 'Claudio Cossio'] | [] | ['ace', 'api', 'confluence', 'node.js'] | 99 |
10,045 | https://devpost.com/software/plana-agile-planner-for-confluence | Plan and organize anything, your way. Plana's boards and lists organize your projects to help you deliver more of your best work, faster.
Collaborate with your team and get more done. Visualize each step of the workflow and see where things are getting stuck.
Keep remote teams on track. Get a clear overview of everything your team is working on – what’s already done and what’s coming up next.
Create scheduling polls and procurement surveys in context.
Hold more effective 1-on-1 meetings with a board featuring agenda, goals, and things to discuss and do.
Inspiration
We use Confluence every day (and night 😉). We come there to plan personal work, team activities, events, project roadmaps, and backlogs. Our teams have their own ways of doing things in Confluence including tips and tricks to get things done fast.
But we still experienced lack of something. 😟 We didn't know what exactly until we looked at our everyday challenges and figured it out. We needed easy-to-use and fast-to-update to-do lists and Kanban-like boards that don't make us go back and forth between editing and viewing pages. 🤔 Not somewhere out there on another site, in another tab. But here, right on this Confluence page. So we made an app for it.😁
It is meant as a quick and simple task and project management tool similar to Asana, but inside Confluence. We are hoping Plana will help other teams just like ours to plan and prioritize work on tasks and projects without leaving Confluence. 💗
What it does
Plana lets users create Kanban-like boards and live lists right on Confluence pages. It brings the framework and structure for:
Remote Meetings (daily, weekly, one-on-one).
Boards for meeting questions, notes, and actions
Team Work.
Shared dashboards to enable each team to stay at the top of the game
Project Planning.
Agile approach for your roadmaps, backlogs, sprints, and resource management
Personal Task Tracking.
Simple planner with your own to-dos right where you need it
Surveys and Polls.
Plan events, gather procurement requests via lists
Key benefits:
Viewing flexibility – switch between List and Board views
Designed for prioritizing and organizing – split tasks in groups and don't get lost in dozens of checkboxes
No need to click 'Edit' – Update list and board items without editing pages
See what's done – Completed tasks are checked and stand out from the others
How we built it
Atlassian Connect, Confluence REST API, AtlasKit, Spring Boot, React, Typescript.
Challenges we ran into
Previously, we didn't use React for developing apps and faced a lot of technical difficulties along the way.
Accomplishments that we're proud of
We have built Plana's UI with Atlaskit components. Previously, we knew almost nothing about Atlaskit, but now we realize how much Atlaskit gives developers and how much faster the app developers can build their apps with it.
What we learned
Technical difficulties while learning a new framework are temporary things. If a team plays as a team, it is a fascinating process that leads you to success sooner or later. And to this submission for Atlassian Codegest :)
What's next for Plana - Agile Planner for Confluence
We have lots of ideas and will be looking forward to
feedback
and feature requests to decide on further development.
The short-term backlog includes:
Custom fields (columns) for dates, assignees, statuses
Calendar view
In-built templates
Built With
atlassian-connect
java
react
spring-boot
Try it out
marketplace.atlassian.com | Plana - Agile Planner for Confluence | Plana helps teams of any size and type plan and prioritize their projects without leaving Confluence with Kanban-like boards and live to-do lists. It is like Asana but in Confluence. | ['Katerina Kolina', 'Alexander Kuznetsov', 'Yuri Orlov'] | [] | ['atlassian-connect', 'java', 'react', 'spring-boot'] | 100 |
10,045 | https://devpost.com/software/blogring | Blogring on a Confluence blog
Inspiration
Blogring is super simple Forge macro that automatically displays a link to the next blog post in a series. We write
a lot
of blogs at our company, and that makes it hard to find the next blog in a series because you have to hunt through a lot of unrelated ones in the navigation bar.
But I'm old enough to remember the '
webrings
' of the 1990s which would link related blogs together with 'Next' and 'Prev' links. So I decided to give that a try for Confluence blogs...
What it does
The macro automatically finds the next and previous blog posts in a series then displays links to them. It can be configured to link just blog posts you created, or link all blog posts with a particular label.
The links are determined automatically, so when you add your next blog post in the series then your previous blog post automatically gets a link to it. No need to remember to go back and update your last blog post!
How I built it
Blogring is a Forge app. I wanted to try a few Forge apps to learn how Forge works, and this idea seemed like a great fit for Forge.
Challenges I ran into
Though this is a super simple macro I did hit a lot of challenges with Forge. I actually find it quite enjoyable to build with Forge — the development process is so quick and simple! — but I did feel the limitations quite a lot. Here's a list of those:
Text alignment:
I couldn't right-align the 'Next' link so it looks out of place. It would look better if Forge could right-align text in table cells.
Macro height:
There is a gap under the links which I think comes from a minimum height for macros. It would look better if macros could be a little shorter.
Date picker indicators:
I tried adding a date picker to let you jump to a day, but it doesn't work well because there is no way to indicate which days have a blog post, and no way to disable days without posts. Some kind of visual indicator of valid days would help.
No action when picking a date:
When you click on a date in the date picker nothing happens. There is no way to take an action when a date is picked, no 'onClick' handler. You have to click a form button to trigger something to happen, which seems unnecessary and isn't how most date pickers work.
No browser navigation:
When you click on a date I can't take you to the blog post for that day, because there is no way for a Forge app to navigate to a different page. So I have to show a link for someone to click on, which is isn't how websites would normally work.
No indication that the config popup is loading:
The configuration popup on the macro can take a little while to render because it has to load a list of page labels first. But Forge doesn't show any loading indicator, so it can feel like it is broken — you click the edit button then wait two seconds with no indication that it is doing anything.
Configuration popup only saves to the page:
The configuration popup can't save shared configuration, such as configuration on the space or user.
No rendering before async functions complete:
Blogring is slower than I would like, it takes a few seconds to display the links because it is searching for matching blog posts first. It needs to do this every time the page is loaded just in case a new blog has been added... however, most the time it's going to return the same result as
last time. It would be so much faster if Forge could instead cache the state between invocations: render the state from last time immediately, then run the async functions to get the latest data — if (and only if) the state changes after those functions then render it again. Most of the time this would make the macro render instantly!
Built With
forge | Blogring | A super simple Forge macro that automatically displays a link to the next blog post in a series. | ['Charles Gutjahr'] | [] | ['forge'] | 101 |
10,045 | https://devpost.com/software/lms-app-learning-management-system | Education Board
Customised Jira ticket for subject
Inspiration
1.37 billion students now home study as COVID-19 school /colleges are close,i.e. nearly 80 % of the student population. Nearly 60.2 million teachers are no longer in the classroom. Student/teacher interaction has changed in this COVID era. The inspiration was to assistant teachers and students during this hard time.
What it does
Jira Based Learning management system (JBLMS) that helps the teacher to run the course and manage the progress of students in remote situations.
How LMS helps teachers?
- Create a study plan suitable for the subject and share with students.
Track progress of the student on boards
Provide tools, learning material
Provide communication links
Adapt the approach if the course becomes too hard or easy for the student
How LMS help students?
Plan study for the subject
Ask for help to teachers if required.
Pace his/her study
How we built it
We have built is using Forge, it not complete yet. We have made progress building education board and customized Jira tickets for schools and colleges.
Challenges we ran into
We were struggling to automatically create students boards from Master boards and update student board if changes are made to master boards. We are using Webhooks to facilitate these interfaces but what we have understood as theory is not working in practice. This will need time and expertise outside our team.
Accomplishments that we're proud of
We have shared this idea in colleges where we study and received very positive feedback. We gather requirement by talking to real teacher and professors
What we learned
We have done guerilla usability testing with students and teachers. We have huge list of features and functionalities that would need to make this fully functional product. We have made a great start in positive directions
Team has learned Forge from Zero.
What's next for LMS App (Learning Management System)
We have to complete 5 important feature that we have identified based on feedback. If we get further traction we would build more features
Built With
forge
react
webhooks
Try it out
geebee.atlassian.net | LMS App (Learning Management System) | Due to COVID 19, 80% of the world's student population is forced to home study. LMS helps teacher and student interactions in the remote classroom situation. | ['VINAYAK M R', 'Jyoti Garg', 'Gaurav Bhargva'] | [] | ['forge', 'react', 'webhooks'] | 102 |
10,045 | https://devpost.com/software/usep-jira-plug-in-user-story-to-effort-predictor | Upload app from below Link https://dev.kornerstoneanalytics.com:8443/atlassian-connect.json
Configure projects for USeP Jira Plugin Step i - Create Project, Click on “Create Project”, Select the type of project to create
- Step iii - Update Project description and default assignee Make sure to choose the default assignee as ‘Project Lead’.
Step iv Add Users to Project roles Click Project Settings, Select People, Select Add people Mandatory User with browse project permission
Step v Configure USeP Project Attributes - Click on USeP Project Configuration link in the left navigation
Step vi Add User Competencies - Click on USeP Project Team Setting link in the left navigation - Click on Add competency
3. User-story to task conversion & generating User Story estimates Step i - Create a User Story in Jira
Click on the User Story to Task
Step ii - Review the predicted tasks User Story to Task link
Step iii - Add new tasks or edit tasks and Accept
Step iv - View the Estimate for the tasks associated with the User Story
Step iv - Product Manager (PM) can accept or override the USeP model estimate. PM can enter his estimate.
Once PM accepts generated estimate and PM estimate, Aggregated task estimate and PM estimate is saved on story-
4. How does a developer commit to an estimate for a task using USeP Step i – Create a task in Jira or Access a task assigned to you
Step ii - Confirm the attributes using USeP Task Confirmation link
Step iii - Access USeP Task Estimate to view Model, PM estimates and commit My_Estimate
Step iv - Commit My Estimate Add your estimate and commit to it
To commit an estimate, press the Commit button.
5. Log time and marking Task complete Step i – Log work time on an issue
Step ii – Mark the issue ‘Done’ a. Select the issue you want to mark done
Mark the status Done. Answer the ‘Happiness Quotient’ query
Inspiration
Very few organizations have team level estimation and actual data for their engineering items. This is the experience gained from working at the helm of engineering organizations, supporting early-stage proposals and bids. The early-stage estimates are rarely collated against the team estimates or actual efforts
We noticed an opportunity to build an Estimation & performance tracking platform based on engineering components thereby helping teams to manage themselves better.
The knowledge base of estimates acts as feed into early-stage estimates, performance and utilization tracking
What it does
USeP
supports the following features
Empowers teams, to manage their estimates and performance thereby ensuring on time and on budget
Convert
User Stories
into manageable standard tasks using
Natural Language Processing
USeP
predicts estimates at a task level which is termed as
USeP Estimates
using Machine Learning
USeP
Aggregates efforts at a
User Story
thereby helping the team to manage cost and effort that goes into building the
User Story
.
Project Managers can be guided by the
USeP
Estimate and make commercial decisions
Facilitates the PM to override the
USeP
to commit to an estimate
Tracks estimate to closure
Collects information as to how happy the developer was in performing the tasks
Provides team level metrics on performance and how much to go
How we built it
The problem of converting a User story to tasks was provided by our teaming partner. A banking customer of our partner needed this problem to be solved in order to track the performance of the team.
Kornerstone Analytics
with its expertise on Machine Learning and Natural Language Processing (NLP) embarked on the problem
We were supported by
Raghu Pasupathy
, a professor from Purdue, USA to help in NLP and attribute identifications
Anita Robin
, a data scientist from Kornerstone Analytics, built the model under the guidance of Professor.
We worked closely with
Amrut Software
to build the plugin, using the connect framework
Akshay and Sushanth teamed to form the BE and FE pair, while Siddharth worked as the technical lead to ensure the environment, tools, and technology were available.
Challenges we ran into
Building USeP Jira plugin has its share of challenges and wins. The founding team is strong, experienced and hence met the challenges halfway
Finances to a bootstrapped project are the first challenge. The development was slow due to this limitation. This had an impact on the team size and mode of operation.
Contracting was our preferred mode of development most of the time. Continuity and ensuring quality was a challenge in this mode of operation
Developing workflow operation screens, iframe sizing issues,
Authorization and JWT token exchange for the connect app
Accomplishments that we're proud of
USeP
platform was adjudged one of the best in a Crowdsourcing event conducted by
Catapoolt
, in the Eastern region,
India
The founder of
Kornerstone Analytics
was chosen to participate in the exchange program supported by
RERISE & Innovation Birmingham's TECH 10 program
during an event, held at WTC Mumbai.
Kornerstone Analytics
represented by
Bharathi Vasanthakrishna
was adjudged
Woman startup of the Year
at the
Aeonian
event,
We are recipients of an
Idea to POC Grant
from the
Government of Karnataka, India
What we learned
Keeping the team together is paramount, and under all odds
carry on
Clarity of communication and display the passion at all times
Small wins ensure enthusiasm within teams.
4.Balance Business needs and technology. Don't allow one to override the other
Customer feedback at all times keeps the idea moving
What's next for USeP - Jira Plugin (USer Story to effort Predictor)
Ensuring that the USep Plugin reached a user base of 10,000 users by the year-end.
Application of the USer feedback to make the Plugin and the Jira environment popular among teams
Providing necessary messaging and analytics as a part of the Jira analytics so that the user draws benefits with the use of this data
Currently, the USeP Jiraplugin includes what is called ‘the happiness quotient’ of the user when
He completes the task. Expanding on this to understand the mood-related aspects and its impact on teams
Built With
celery
docker
flask
gitlab
google-cloud
google-natural-language
gunicon
java
kong
letsencrypt
microservice
mysql
postgresql
python
slack
spring
springboot | USeP - Jira Plug in | Convert USer Stories into tasks and estimates based on past data. Integrates with JIra and provides a seamless view to the developer world. | ['Bharathi Vasanthakrishna', 'Vishwajeet Singh'] | [] | ['celery', 'docker', 'flask', 'gitlab', 'google-cloud', 'google-natural-language', 'gunicon', 'java', 'kong', 'letsencrypt', 'microservice', 'mysql', 'postgresql', 'python', 'slack', 'spring', 'springboot'] | 103 |
10,045 | https://devpost.com/software/workplace-confluence-connector | Confluence page to be shared as a Workplace group post
Instant sharing to Workplace
Workplace group post originating from the Confluence page
Comments added to the Confluence page
Automatically synced comments in the Workplace post
Inspiration
We work for a company that uses both Confluence Cloud and Workplace by Facebook. Whenever a particularly important announcement or policy is created, it is often shared in both platforms. This means that the authors must spend time and effort to publish the same content twice. And the more frustrating part is that user comments are spread between 2 places and not synced with each other, so the visibility of comments and questions asked by other users is much less. This app will make sharing any important announcement, or information much easier.
What it does
Workplace Confluence Connector allows Confluence space admins to map their spaces to dedicated Workplace Groups. Then, whenever content in the space needs to be shared to Workplace, clicking a content action converts the content to markdown and posts it to the target Workplace group. Moreover, any comments that are added to the page are automatically synced with the Workplace post so that no update or discussion is missed.
How I built it
We used Atlassian's new Cloud development platform called "Forge".
Challenges I ran into
There were some challenges associated with using Forge in its beta such as:
Limitations around web triggers and handling of query params.
Given the sandboxed nature of Forge, React or arbitrary HTML can't be used in the Forge app. We had to rely on a somewhat small (albeit rapidly growing) component library.
Frequently released breaking changes.
Accomplishments that I'm proud of
We are proud to have created one of the first integration apps for Confluence and Workplace.
What I learned
How to use a completely new development platform for Atlassian Cloud apps.
Better understanding of Workplace APIs.
What's next for Workplace Confluence Connector
This app is a prototype and was just built for this hackathon. There are a lot of ideas that we want to implement in the app to give its users more options and flexibility such as:
Sending messages to Workchat conversations from Confluence.
Convert Workplace posts to Confluence pages.
Built With
forge
javascript | Workplace Connector for Confluence | For Confluence and Workplace users who often use both platforms to publish the same content. This app saves time and effort and ensures uniform delivery of communication across both platforms. | ['Ahmed Al-Aghbari', 'Abdullah T'] | [] | ['forge', 'javascript'] | 104 |
10,045 | https://devpost.com/software/benkobot | Inspiration
When I first started using Butler in 2016 it was absolutely mind blowing. I had started doing some automation of Trello using Google Apps Script from the Little Blue Monkey "Pimp Your Trello Cards" script, but Butler was totally next level.
In February 2018 they told me I wasn't allowed to use it as a consulting platform anymore, after I had spent a year building complex business systems for my clients using the platform, so I built Trellinator, an open source framework for automating Trello (and other things) using Google Apps Script. I then ported all 1,800 Butler commands that I had written for my clients, over to Trellinator.
Even though some people other than me and my clients use Trellinator, the barrier to entry setting it up as a Google Apps Script is so high that most people fail to get started.
I had the idea to build a "hosted Trellinator", and BenkoBot was born!
What it does
BenkoBot is a hosted and secure environment for executing Trellinator code to quickly and easily create Trello API automations.
How we built it
The biggest challenge was getting a secure way to execute user submitted code. I followed an example from a Medium post on how to use docker combined with gvisor and the Node.js "vm2" package to create a secure sandbox that is capable of executing code, and also allowing external access to other APIs without exposing the underlying file system.
We used beanstalkd as the work queue to handle the long running process of executing the code in a docker container on a GCP cloud instance, and stuck a really basic "quick n dirty" PHP frontend on it to test it out.
We actually have a much nicer React interface on the way, but couldn't get it running in time for the submission deadline. It might be online by the time you test it out though ;)
Challenges we ran into
Getting the secure code execution under docker working really smoothly and allowing easy use of external APIs while still keeping the "sandbox" secure took up a lot of time. The challenge then was racing to build a nicer looking interface, but we figured it's better to have something that works and proves the concept, and looks terrible, rather than something that looks nice but doesn't run!
Accomplishments that we're proud of
The code execution backend is super robust and secure. It sits on a separate cloud instance that's not web accessible, and communicates with the frontend via a beanstalkd queue, so the user can have long running code executing and the interface can remain responsive. This will also allow easy extension into handling notifications and scheduled jobs.
What we learned
How to do secure code execution using Node, docker and gvisor! Also that CloudRun is great for hosting docker containers but that it doesn't work sometimes for weird reasons (part of the reason why our slicker looking interface isn't online!)
What's next for BenkoBot
Well, as mentioned, getting a better interface online.
Once we have that, we will be adding in all the Trellinator features:
Handling notifications (when this happens, do this)
Scheduled executions
Installing functionality on individual boards, groups of boards or globally
Account management/multiple credential handling (for example so consultants can easily write code for multiple clients)
Bitbucket integration so that all your code is version controlled, and also so you can build and test in your own environment then deploy with a post commit hook to BenkoBot
Built With
beanstalkd
docker
google-cloud
gvisor
html
node.js
php
trello
Try it out
app.benkobot.com | BenkoBot | BenkoBot is like ScriptRunner for Trello. It picks up where Butler Bot left off by providing a powerful and easy to use, hosted wrapper for Trello's API based on the open source Trellinator framework. | ['Iain Dooley', 'Kynan Stewart'] | [] | ['beanstalkd', 'docker', 'google-cloud', 'gvisor', 'html', 'node.js', 'php', 'trello'] | 105 |
10,045 | https://devpost.com/software/forge-unsplash | Inspiration
Unsplash is a website dedicated to sharing stock photography. The website claims over 110,000 contributing photographers and generates more than 11 billion photo impressions per month on their growing library of over 1.5 million photos.
What it does
Makes it a breeze to incorporate the beautiful HD photography of Unsplash into the joyous confines of Confluence pages.
How I built it
Blood, Sweat, Tears
Challenges I ran into
Inconsistent Forge Documentation and Low Unsplash rate limits
Accomplishments that I'm proud of
That I stayed sane after this experience
What I learned
That it was a mistake quitting my day-job
What's next for Forge-Unsplash
World domination
Built With
forge
Try it out
github.com | Forge-Unsplash | Make it a breeze to incorporate the beautiful HD photography of Unsplash into the joyous confines of Confluence pages. | ['Krishna Kumar'] | [] | ['forge'] | 106 |
10,045 | https://devpost.com/software/sketch2code | Inspiration
What more could we accomplish if the time to test an idea was zero?
I've been in awe of what computer vision can accomplish and how it can bring about positive change in our business processes. One such area is UI prototyping. Sketch2Code made me rethink the efficiency of existing accepted process by demonstrating the utitlity of AI and computer vision in producing prototypes for user testing. I got the idea that integration with tools such as Jira and Confluence would make it readily accessible and fit seemlessly in the users' collaboration space while also making them far more efficient.
What it does
Sketch2Code Block allows one to transform a UI sketch into a working web interface within seconds. If you have sketch anywhere, just click a photo and add it to your Jira issue as attachment or add it to your confluence page by providing its URL in the configuration of the Confluence Macro.
Users viewing your Jira Issue or Confluence page can simply click on generate code to see the resulting web page of the UI Sketch(es) you added.
How I built it
Forge SDK
Microsoft Azure Cloud and Customvision.ai
Challenges I ran into
Understanding how Forge UI works and figuring handling interactions on Server side was a bit of mindset change.
Debugging was really fast paced due to
forge tunnel
command, however error messages were sometimes cryptic.
Accomplishments that I'm proud of
Training a custom vision model that performs well for a very small dataset of about 140 images with 10 classification labels.
Building a easy to use extension that integrates with and enhances the design proccesses.
What I learned
Atlassian's new Forge platform
Azure Cloud
What's next for Sketch2Code Block
Real time multi-party collaboration on Sketches (Google docs for UI sketches).
Faster code generation.
Better HTML generation with more training data.
Built With
atlassian
azure
confluence
customvision.ai
forge
jira
Try it out
github.com | Sketch2Code Forge App | A new way to test your designs! Transform UI Sketches to HTML Web Page in seconds. | ['Piyush Agrawal', 'Shashwat Gulyani'] | [] | ['atlassian', 'azure', 'confluence', 'customvision.ai', 'forge', 'jira'] | 107 |
10,045 | https://devpost.com/software/meetings-and-decisions-addon | PDF Report
Dashboard
Discussing a topic
Meeting View
Inspiration
With the COVID-19 pandemic we discovered new ways of working remotely and identified the need to improve the way we were keeping track of meetings and team decisions.
What it does
This addon helps you to keep track of your meetings, structure the ideas to be discussed, and manage decisions that are concluded from these meetings.
How I built it
We use Atlassian Connect, NodeJs, React, AtlassKit
Challenges I ran into
Technical Challenge: Using React with Atlaskit
Product Challenge: Designing a new way for teams to have a structured and organized meeting, presenting the decisions made during the meetings to the rest of the team.
Accomplishments that I'm proud of
This addon uncovers a new way to target meeting goals
What I learned
Atlaskit is awesome!
What's next for Meetings and Decisions Addon
Advanced settings
Permissions
Diagrams
File uploads
Built With
ace
atlaskit
mongodb
node.js
react
Try it out
sync-meetings.herokuapp.com | Meetings and Decisions Addon | Meetings and Decisions Addon | ['Francisco Gerardo Neri Andriano', 'Kathia Alexander', 'Hector Benitez'] | [] | ['ace', 'atlaskit', 'mongodb', 'node.js', 'react'] | 108 |
10,045 | https://devpost.com/software/jframe-iframe-and-embed-code-dashboard-gadgets-for-jira | Embed Jira dashboard gadgets from various vendors, including Google & Microsoft services, Figma, CodePen any many more
Create your own personal dashboard with your calendar, graphs, maps, playlists and more
Look for the "share" or "embed" option, or try embedding a web page by using its URL address
jFrame
iframe and embed code dashboard gadgets for Jira Cloud
Inspiration
Making the process of embracing new tools more agile
The modern work environment demands an increasing stack of tools. The more we work with remote teams the more it'll continue to grow, and Jira will always be at the center the workflow. As users, we embrace new tools and the good they bring, but we want to keep the learning curve and dependence on admins low. As Jira administrators, we want reliable tools that meet everyone's needs with less integration concerns. This usually leads to cumbersome processes, and we really wanted to help bring agility to this issue.
Learning from Jira features like Automation and Next-Gen, we realized we want a powerful generic product that is securely controlled by the users with great defaults. We came to realize dashboards are used in various ways from personal/functional ones to a team/company wide ones, and provide various known and easy to control permission mechanisms, while the modern open web offers a variety of embed options from providers who are eager to get their products easily integrated.
Thus, the idea of jFrame was born!
What it does
jFrame is a dashboard gadget designed to help users embed external content from many different platforms with minimum effort and maximum results. The gadget will accept and analyze your embed code or plain URL into useful needed settings, leading to an easy and successful embed. Not every web content out there can be used like that, but our API keeps growing and supporting more and more. Combining our API with some unique GUI features and opt-in settings control, helps our users really get the right result in terms of appearance, functionality, and even security.
How we built it
We use a server-less architecture hosted on AWS to integrate with Jira Cloud with the Atlassian Connect framework. This is how we power our AtlasKit app, bringing a smooth experience to our users. We keep our stack as up to date as we can, though some old school knowledge of vanilla JS/CSS/HTML/HTTP and more web/industry standards is crucial for this task.
Challenges we ran into
Creating a simple yet useful user interface while dealing with multiple variables was the most challenging part. Sure it's a hard task to go into integrating the unknown while being integrated into Jira, and any old school web developer will tell you horror stories about and
iframe
inside an
iframe
, but we anticipated all of that technical and bureaucracy pain. After all, taking this on us is part of what the app provides for it's users.
Accomplishments that we're proud of
jFrame
is more than just an
iframe
- it's a
a complete and growing product!
We started as a plain
iframe
making our first steps at the Atlassian Marketplace, but it didn't stay like that for long. The first set of features was aimed making sure the embedded content is integrated correctly, adding unique features for responsive/fixed sizing and controlling the interactivity. Soon after that we introduced our new embed wizard and the analyzing API with best fit suggested defaults. But the biggest accomplishment for us is learning to understand our users better and what our product can give them in the future.
What we learned
The best thing about creating this app is how much we learn. We knew there are a lot of useful platform supporting embed codes out there, but actually seeing them in action, really made us learn a lot more about the potential jFrame and Jira dashboards have in making our day to day more effective. And the learning never stops when you have your users bringing in new embed ideas over the ones we already test and use in our own work day to day.
What's next for jFrame
There are already new features waiting to be released making the gadget even more powerful, but we are not going to stop there. Organizations can benefit more from the app, and we our research on more Jira user needs lead us to start planning how we can help outside of our dashboard gadget too.
Some high level highlights:
Supporting every possible provider out there while keep security and privacy demands.
A wide and surprising set of presentation and appearance options.
Allowing embed of multiple sources into one gadget.
Central control with admin control.
Integrating into Jira outside of dashboard gadgets.
The rest is left for your imagination...
You can always use the "Watch app" button in
our marketplace listing
for more updates, but we recommend the "Try it free" button and becoming part of our embed family.
Built With
amazon-web-services
atlaskit
atlassian
atlassian-connect
bitbucket
css
html
http
javascript
jira
json
react
xml
Try it out
marketplace.atlassian.com | jFrame - iframe and embed code dashboard gadgets for Jira | Embed straight from your favorite platforms into Jira dashboard gadgets with zero learning curve and no integration efforts required from administrators | ['Addown Studio'] | [] | ['amazon-web-services', 'atlaskit', 'atlassian', 'atlassian-connect', 'bitbucket', 'css', 'html', 'http', 'javascript', 'jira', 'json', 'react', 'xml'] | 109 |
10,045 | https://devpost.com/software/word-cloud | GIF
Word Cloud Gif Example
Inspiration
From typical word clouds that are fun and interesting.
What it does
This Word Cloud app represents the most commonly used words within a JIRA issue through the text size and opacity. You can also re-generate the Word Cloud which will change the positions. There is also a filter for common words such as 'the', 'and' , etc.
How we built it
Using SVG to display the words and the styles. And Forge (of course!) to get the JSON from the issue.
Challenges we ran into
Initially, we were planning to use CSS styling on components to display the words (and have the ability to stack them automatically) but was unable to find a way. Forge accepted certain parameters in the UI components so trying to tie it with style didn't work. This resulted in us using SVG to display the words.
Accomplishments that we're proud of
We finished a working Forge App!
What we learned
We learnt how to use Atlassian Forge, collaboration skills, more Javascript ES6 and how SVG works.
What's next for Word Cloud
Better styling (more colours and spaced out words for clarity) and possibly animations.
Built With
forge
javascript
Try it out
bitbucket.org | Word Cloud | This will display a Word Cloud (words with most occurrences) in Jira according to the opened issue. | ['Judy Lim', 'Taylah Contemplacion', 'Chitra Sajikumar'] | [] | ['forge', 'javascript'] | 110 |
10,045 | https://devpost.com/software/motivapp | Our project
Let us introduce Motivapp, the Atlassian forge app, which provides your team with the possibility to see top creators / top likes / top commentators right on the Atlassian platform.
Motivation is the key to efficient teamwork. The application we’ve done keeps the team informed because Motivapp provides your team with the possibility to see their contribution in a single interface right on the Atlassian platform.
During the work, you are able to create a new document, comment it, and like it.
If you come back or open Motivapp you can easily check what position in a list do you have.
Our application is very simple to use. The interface remains very intuitive and user-friendly. Therefore our extension is almost ready to use it on the Atlassian platform.
Thank you very much for your attention!
Built With
atlassian
forge
javascript
react
Try it out
github.com | Motivapp | Our idea is to create an app that would hopefully motivate people to write better files and be more active through encouraging them by displaying the productive ones with our app. | ['Mike Petrov', 'Александр Бутенко'] | [] | ['atlassian', 'forge', 'javascript', 'react'] | 111 |
10,045 | https://devpost.com/software/speedy-pdf-sign-offs-for-jira | Configuration: Customer's google drive is linked. All records will be stored there.
Configuration: Jira admin can connect either a Google drive or an AWS bucket
Starting signing a Speed-eRecord
Start signing on a Speed-eRecord
All Speed-eRecords can be viewed from the Issue view
Signing on a Speed-eRecord
Completed signing a Speed-eRecord
Speed-eRecords are beautifully designed and embed all issue attachments as part of the PDF
Inspiration
For several years, RadBee has helped heavily-regulated life science enterprises handle their sensitive business, product development, and compliance issues through the Atlassian ecosystem.
While Jira has served as an excellent method to develop products and track and resolve issues, it is difficult to capture Jira data at a precise point of time along with any official approvals. Users today are forced to find slow workarounds to solve this gap.
This inability to quickly and easily capture the ‘control event,’ or the precise moment in time when an issue is reviewed, resolved, and approved, has long-ranging implications to the organization’s ability to pass critical audits, and more.
For example, enterprise users need to prove that:
Industry-specific testing processes were followed when a product is ready to be publicly released
Security and vulnerability management processes were followed by the team or enterprise
All required documentation was provided, reviewed, and signed during hiring processes
And more!
RadBee wanted to help the enterprise capture the data in Jira in that perfect moment in time, the control point, and have it easily signed off and archived without slowing down agile teams. We also aimed to:
Create an easy installation process that takes just seconds so as not to slow down critical work on the team.
Make this capability immediately available to all projects in Jira, so that every team and project can start using the app as soon as it's installed.
Provide the ability to self-select an eRecord archiving destination separate from Jira. As the eRecords are sensitive and auditable, their retention should not be dependent on the Jira issue, especially in the event that a Jira issue is deleted.
Provide a beautifully-formatted, standalone PDF eRecord that can be viewed independently of any external resources. It also had to embed issue attachments that contain critical data. In our experience, we know that these eRecords are often seen by customers and audit teams, and wanted to ensure a professional, well-formatted, and audit-ready record which helps build trust.
Not retain any customer information on our side. The only time we have customer data is when the App generates the PDF file.
What it does
Speedy PDF Sign-Offs for Jira helps fast-moving teams capture official sign-offs and document issue resolution and approvals without slowing down their flow.
Able to handle any Jira issue, the enterprise app creates a beautifully formatted Speed-eRecord of the particular moment in time, which can be electronically signed and archived safely in a matter of seconds.
SpeedyPDF SignOff takes seconds to install, and is immediately available to support your entire Jira instance, projects, and issue types.
How I built it
Speedy is an Atlassian Connect app.
It runs on a Google Cloud infrastructure:
The UI Components and the functions who interface between Jira and the PDF generator are running on Google Firebase. These parts are built on TypeScript, NodeJS and React.
The PDF generator uses Google Cloud Run. This part is built in Java.
Challenges I ran into
What's the best technology to use when transferring Jira data into a PDF?
This was a key question with system-wide implications about the end product. We did not have specific background in PDF, or in PDF generation engines and technologies, but we still wanted to create a beautiful PDF which will be archive ready. We spent a long time in this technological exploration and eventually landed on a solution, which is in line with the state of the art in this area.
We retrieve Jira data in json format (based on Connect rest calls) and pass it into our PDF generator. The PDF uses velocity templates to generate HTML data which is then processed by the iText PDF library (commercial library) to generate the PDF.
Embedding attachments in the PDF was a big issue
The ambition to include the embedding of attachments as part of the Hackathon proved to be our most expensive decision in terms of resources. It required close collaboration and synch accross our interfaces and required us to implement a much more complicated hand-over mechanism (from Jira to the PDF generator).
No memory principal
We did not want to hold onto customer information for the long term, but still had to have a 'long term' process. The first time we process a Speed-eRecord is upon its creation, and the second time is when the last signature is received and signature tables are added. Keeping in mind our design principal of not storing 'historic' Speed-eRecords, the processes required some very careful design that impacted the PDF itself, customer storage management, and the properties we keep in Jira.
Client storage connectivity
We wanted to demonstrate the principal of storing the Speed-eRecord in a location assigned by the customer. To show that the app is "storage agnostic," we wanted to have at least two types of storage locations. We initially wanted to have Confluence be one of these location, but this seemed to be more then we could fit in the time we had.
Eventually, we chose these two types:
Google Cloud - because this is very easy to set up and is tremendously popular.
AWS Bucket - could make sense as a storage location to organisations who have AWS as their chosen platform. It requires some AWS know-how, so we worked hard on making the setup as self-explanatory as possible.
Need to access the Connect eMail API meant we needed to wait for approval from Atlassian
As it is, the processing of the specific approval process to access the email API by Atlassian is long. It took us three weeks from the time we raised the request until we had access. That was nerve-wracking and meant that the complete email channel could be closed only on the last Friday before the Hackathon deadline.
Accomplishments that I'm proud of
From concept to app in few weeks:
The work on the app was triggered by the Codegeist competition. Everything that we're submitting today is the result of intense work happening over the last six weeks; juggling between the Hackathon and all the other projects and life chores we are busy with.
Finally using Connect:
RadBee usually works on Server. This was our first development experience with Atlassian Connect. Our team was joined by people who had good knowledge in the area, but this was still a big learning curve for many.
Collaboration:
Our app was built in collaboration by two teams who had no collaboration history. We still managed to work effectively and deliver the app, working remotely across four different time zones.
Result:
While the Codegeist submission is not "feature complete," it is consistent with the product vision we had and is built on design principals which will allow us to complete the features on the same foundations. Specifically:
The infrastructure to embed attachments in the PDF is there.
The principals of managing a "long process" (the creation of PDF and then adding the signatures) have been understood and implemented.
What I learned
Hackathons are great fun and a good way to skill-up and alleviate any blues caused by the Covid-19 pandemic.
Lots of technical stuff, key areas already mentioned above.
What's next for Speedy PDF Sign-Offs for Jira
Speedy PDF is now in Beta, and we invite anybody to try it out. It's currently pending approval on the Atlassian marketplace, but anybody who wants access can send us an email to:
[email protected]
We have a long list of stories in our backlog, so for us, our journey has just begun.
Built With
firebase
html
java
jira
node.js
pdf
velocify
Try it out
radbeedocs.atlassian.net
marketplace.atlassian.com | Speedy PDF Sign-Offs for Jira | Speedy PDF Sign-Offs for Jira helps fast-moving teams capture official sign-offs and document issue resolution and approvals without slowing down their flow. | ['Rina Nir', 'Dmitrii Saltykov', 'Eduard Grinchenko', 'Tamara Bazko'] | [] | ['firebase', 'html', 'java', 'jira', 'node.js', 'pdf', 'velocify'] | 112 |
10,045 | https://devpost.com/software/disastr-code | Ring of Fire
Disaster Zone
Affected
Inspiration
Our county experiences frequent natural disasters because the archipelago was formed from a very long evolutionary process, due to tectonic movements. It has been called the "Ring of Fire".
What it does
Ring of Fire: Disaster Response System involves risk mitigation, disaster prevention activities, emergency response, and rehabilitation. It includes:
pre-disaster/mitigation
emergency response
post-disaster/rehabilitation
The application is intended to be used by:
(Affected) residents
Relief organizations
Government, and/or other entities.
How I built it
EC2
AWS Sagemaker to build machine learning models.
Datasets: NexRAD on AWS
Challenges I ran into
predict damage to houses, buildings, and public facilities (schools, hospitals, etc).
What I learned
Develop machine learning model for the disaster response system
What's next for Ring of Fire
Post-disaster rehabilitation and reconstruction system.
Built With
amazon-web-services
sagemaker
Try it out
github.com
vvb2nms7wk8i4lw.studio.us-east-2.sagemaker.aws
www.youtube.com
www.youtube.com | Ring of Fire | Disaster Response System | ['Tri Labs'] | [] | ['amazon-web-services', 'sagemaker'] | 113 |
10,045 | https://devpost.com/software/meet-with-jitsi-atlassian-forge | Meet with Jitsi - app benefits
Meet with Jitsi - Confluence content byline item and start/join meeting dialog
Meet with Jitsi - join meeting on public Jitsi instance
Meet with Jitsi - Confluence configuration tab
Meet with Jitsi - Jira issue glance and start/join meeting dialog
Meet with Jitsi - join meeting on private Jitsi instance
Inspiration
The ongoing COVID-19 pandemic is redefining the way teams work, and even though we all hope being able to meet colleagues in person again soon, the evolving remote work scenarios are here to stay.
The resulting surge in video meetings is now part of most people's daily life, and the video conferencing market has boomed, with notable participants like Microsoft Teams, Slack's new collaboration with AWS to migrate their custom solution to Amazon Chime, and of course Zoom with all its privacy and security flaws.
There is also also the fantastic and still not widely known browser based alternative
Jitsi Meet
, which is a
fully encrypted, 100% Open Source video conferencing solution that you can use all day, every day, for free — with no account needed
. It provides similar features to commercial solutions, can optionally be self-hosted, and has a slick mobile app as well, what's not to like?
We at
Utoolity
have been using it via a
custom deployment on AWS
for quite a while, both for our team communication and during customer support. It feels very empowering to have an easy to use and basically free video conferencing solution without any prerequisites, and most importantly, without any privacy and security concerns attached.
We want to make it even easier to use by providing a contextual meeting URL right from a Jira issue for support interactions, or from a Confluence page for sprint planning and more – meet
Meet with Jitsi (Atlassian Forge)
.
What it does
Meet with Jitsi provides a two click experience to start or or join a meeting from a Jira issue or Confluence page. It presents a dialog with the meeting URL and allows to override default options so that users can join muted, or opt-out of the otherwise preferred peer-to-peer (P2P) mode for 1-to-1 conversations, which doesn't work well on low bandwidth connections.
These options can be defaulted per project/space, including the base URL for the Jitsi instance (defaults to
https://meet.jit.si/
) and team prefix (defaults to the Atlassian Cloud sub-domain). In Confluence this is achieved via the readily available
SpaceSettings
component, in Jira we use an
IssueAction
as a workaround for the missing
ProjectSettings
component.
How we built it
We used the Forge CLI to quickly explore the various Forge modules to identify applicable UI components for the use case. We then started over with the app itself and have refined it since, which mostly meant finding sufficiently usable workarounds for encountered UX issues based on Forge UI limitations.
The Forge CLI's excellent DX makes all this a breeze, so it is a great prototyping tool for Atlassian apps in general.
Challenges we ran into
The declarative approach of Forge UI is conceptually appealing, but the resulting UX and layout restrictions leave a lot to be desired still, even for small and straight forward use cases like this one.
Also, the absence of a Jira equivalent for
SpaceSettings
requires a workaround that now exposes the settings to customers (we can remedy this by removing the issue action of course). Most importantly, the absence of any kind of secure app scoped settings basically means that any logged in user can override the settings via the REST API, which is a security flaw for many use cases (see
FRGE-43
and
FRGE-46
).
We hope that the Atlassian Team will iterate quickly on providing additional modules and UI components, and more importantly, a few layout and design options so that elements can be presented in more flexible ways in dialogs, forms, and tables.
Accomplishments that we're proud of
We are really happy that the app is cross-product from the get go and works identically in Jira and Confluence (ignoring the missing project level configuration Forge UI in Jira, which will hopefully be available soon).
What we learned
We learned the ins and outs of developing a cross-product app on Forge, which highlights the benefits of the unified declarative UI, while also surfacing its current limitations in terms of an almost generational reset to table and spacer based layouts. We appreciate that a restricted set of UI components ensures a consistent user experience, but the current limitations still seem to be too significant for many use cases, in particular for commercial apps.
Based on the excellent Forge CLI DX, we also intent to use a 'Forge first' development approach for our Cloud apps going forward, because the limitations force you to stay laser focused on the customer value, while ignoring UI/UX bells and whistles during the prototyping phase. This eases developing a domain model and the backing API/SPI so that the app core remains independent from the frontend technology. Whether or not an app still requires the currently superior UI versatility of Connect then depends on how the Atlassian Cloud platform evolves over the coming months and years.
What's next for Meet with Jitsi (Atlassian Forge)
We would very much like to make this app available to users via the Atlassian Marketplace, so depending on the ETA for the public distribution of Forge based apps, we might need to migrate the app to Atlassian Connect on the short term. That's no big deal given its static characteristics, but still a pity, because once we do and need to create a likely more appealing AtlasKit based UI anyway, migrating back without disrupting users will be difficult.
Feature wise we are contemplating how to promote a meeting to a self-contained entity so that meetings can be scheduled and become possibly long-lived resources including links to the agenda, the meeting notes, and the recording. Based on feedback, we might also provide more customization options for the meeting URL, for example by using the more memorable Confluence page name.
Also, we will refine the CloudFormation template that provisions a custom Jitsi Meet instance on AWS so that it gets more cost effective and scalable. Low hanging fruits are splitting the current monolithic
Jitsi Meet on Docker
image into the underlying four services that can then be independently autoscaled on
Amazon ECS
and
AWS Fargate
.
Built With
atlassian
confluence
forge
jira
Try it out
go.utoolity.net | Meet with Jitsi (Atlassian Forge) | Start or join a contextual Jitsi video meeting right from your Atlassian Jira issue or Confluence page | ['Henrik Opel', 'Steffen Opel'] | [] | ['atlassian', 'confluence', 'forge', 'jira'] | 114 |
10,045 | https://devpost.com/software/actonic-report-builder | Actonic Report Builder - one app for any report you might ever need!
Most popular visualization libraries included & ready to use
My Reports | Share Reports | Gallery
My reports
Report Gallery
Example of a network chart
Example of a line chart
Edit Template
Edit Script
Syntax highlight, autocomplete for Javascript and HTML
Could anyone imagine machine learning directly in Jira? Our app is packed with cutting-edge libraries and can even classify toxic comments!
About Actonic
Actonic Team has been working in IT Consulting for over 17 years. We have helped hundreds of businesses of all sizes fulfil their potential by thoroughly analysing ways to improve communication and collaboration and optimise processes.
Inspiration
In many cases, using Atlassian ecosystem appears to be the best choice for companies striving to become more flexible, adaptive and agile, however, built-in functions rarely meet all the requirements, especially when it comes to reporting. While optimizing customers’ infrastructures, we've often been asked to set up the process to properly track and measure team efforts. We have seen a huge demand for such a tool, but haven’t been able to find the solution that would effectively meet our requirements. Therefore, we’ve decided to create our own app with customers’ needs in mind.
Actonic Report Builder
We are preparing a one of a kind tool to create ANY reports for Jira Core, Software, or even Service Desk. It will be not just a Jira add-on building a couple of reports, but a complete framework allowing Jira users to create any type of reports using their favorite visualization libraries - directly in Jira, without developing their own add-ons, only using JavaScript and HTML. The initial version will offer integration with the most popular libraries such as D3, Google Charts, Chart.js, vis.js, moment.js and a few more. We hope that
Actonic Report Builder
will help customers save time, hit deadlines and stay on top of their time!
Actonic Report Builder
is already available on the Marketplace!
Built With
atlassian
chart.js
d3.js
google-chart
javascript
moment.js
node.js
react
Try it out
scripted-reports.actonic.io | Actonic Report Builder | Comprehensive reporting framework helping Jira users to create any reports using their favorite visualization libraries (D3, Google Charts, Chart.js) directly in Jira, without developing their own app | ['Andrei Pisklenov'] | [] | ['atlassian', 'chart.js', 'd3.js', 'google-chart', 'javascript', 'moment.js', 'node.js', 'react'] | 115 |
10,045 | https://devpost.com/software/page-view-counter-for-confluence-rycv8g | Inspiration
Want to see popularity of the pages on the page itself.
What it does
It counts page visits and displays on the page.
How I built it
I build it with forge.
Challenges I ran into
Accomplishments that I'm proud of
Can see page counter on confluence page, and got first app with forge working.
What I learned
How to build forge apps.
What's next for Page View Counter for Confluence
Switch to get data from analytics API when available (as far as I know it is not available at the moment)
Add graphs, and more analytics fields.
Built With
forge | Page View Counter for Confluence | Add page view counter to confluence page with simple macro. | [] | [] | ['forge'] | 116 |
10,045 | https://devpost.com/software/semantica | Inspiration
CQL search allows user to use complex filters and search for specific information beyond what is possible using native Confluence search. However, a regular user might not know how to use CQL because using CQL requires training and understanding. By allowing user to use natural language to perform CQL query, we aim to allow regular users to perform complex query using a language they are already familiar with.
What it does
Translates natural language to CQL query to search for content (pages, comments, etc.)
How we built it
We used Dialogflow API to transform natural language query to structured data which in turn is used to generate CQL. We use the generated CQL to call Confluence REST API.
Challenges we ran into
Initially we wanted to train our own model which translates natural language to CQL in one step without the intermediate structured data, but was unable to do so because we did not have enough data to train an accurate model.
Accomplishments that we're proud of
We successfully translated natural language to CQL and use it to search for content.
What we learned
The model provided by Dialogflow does not need a lot of data to train but the data needs to be annotated by hand as to which part of the sentence corresponds to which CQL field. On the other hand, the model we initially wanted to go with requires a lot of data but it doesn't need annotated data and can predict accurately given enough examples.
What's next for Semantica
Train the model in Dialogflow to be able to understand more complex sentences.
Build a similar search for JQL using natural language.
Built With
atlaskit
serverless | Semantica | Perform CQL search using natural language | ['Brigitte L'] | [] | ['atlaskit', 'serverless'] | 117 |
10,045 | https://devpost.com/software/wisdom-of-crowd | Homepage
Create New Session
Filling in all the details for a new session
People and Time form completely filled
Questionnaire Builder
On clicking add question button, a modal pops up asking question details
Filling up of options to choose from for certain types of questions
A completely filled questionnaire builder
Session dashboard table view - 2
Session dashboard card view - 1
Enter answer
Waiting for players to answer
Choose answer from list
Waiting for players to choose answer
Multiple choice
Rating
Ranking
Checkboxes
Dropdown
Yes/No
A final report contianing all the session details
On clicking the options, a modal pops up showing how many votes did each option get
Wisdom Of Crowd
An Artificial Intelligence powered real time multilingual team voting application built with Atlassian's connect framework.
View the demo »
Table of Contents
About the Project
Inspiration
Difference
Built With
How it works ?
Components and App Walkthrough
Step 1
Step 2
Step 3
Step 4
Question Types
Step 5
Session Types
Step 6
Step 7
Question and Answer Round
Step 8
Step 9
More about the libraries used
Bitbucket Link
Roadmap
License
Contact
About The Project
Wisdom Of Crowd video
An AI powered realtime team voting app to make better decisions. The first distinct quality that separates us from other similar platforms is the customisability/flexibility that we offer. The exhaustive coverage of the various forms of discussion encompassed in a single multilingual group chat platform, to ensure a comprehensive exchange of ideas and conveying of ideas.This completely changes the way remote teams work. This app make use on Atlassian's connect framework and Jira's rest api along with AWS's Translate and Polly for AI.
Inspiration
The inspiration of this came to us while pitching an idea to a group of friends, who all had their opinion regarding it, so we decided why not create something which enables us to easily take a note of each other's opinion and analyse it efficiently to move forward with the idea/project and give a direction to it. It can be efficiently used for effective decision.
What separates us from the other similar chat platforms?
The first distinct quality that separates us from other similar platforms was the customizability/flexibility that we offer. The exhaustive coverage of the various forms of discussion encompassed in a single group chat platform, to ensure a comprehensive exchange of ideas and conveying of ideas is something that this idea has brought forward.
Highlight Features
Real time voting
7 types of questions
Real time language translation in 11 languages
BarCharts and PieCharts for each question
A dynamically generated PDF report
AI powered video generation
How it works ?
The app allows you to take an opinion on your idea by asking questions about the same to your fellow team members, the results are displayed instantly in the form of
bargraphs
and
piecharts
along with a Pdf report of all the details about the questions asked. Our app also provides
dynamic video generation
of the data presented as well as
real time language translation
options
using AI
, so that you friends can give an opinion in their own language, this in turn helps you to take a better approach to give a direction to your idea.
Also, this app takes advantage of the
Atlassian's Connect framework
and
Atlaskit UI
along with
JIRA's Rest API
to provide a platform to raise issues and generate ideas along with the benefit of team voting, to get real time statistics of the data. Not only this with the integration of
slackbot
and
AWS Rekognition
, along with
AWS Translate, AWS S3 and AWS Polly
, the functionalities it becomes capable of doing are limitless.
Want to know more about it's features ? Checkout the link below:
Wisdom of crowd features
Components and App Walkthrough
Before starting add members to your Jira workspace you need to add all your team members in a group named 'wisdom-of-crowd' in order to choose and invite members to the session.
Step 1
Home Page
You are welcomed with the home page of the app, which has a create new Session button.
What is a Session ?
A Session is basically a Q/A round you play with your team mates.
On clicking the button you are taken to create a session page.
Step 2
Create Session Page
On create wisdom of crowd session page a form is shown to fill out the session details, in order to store the data in the database.This allows you to create a new session, by filling in :
Session Name
Session Description - telling what it's about
Number Of Questions - the number of questions you want to ask for that particular session.
On submitting the form the data is added in the database and you are now directed to
Add people and time page
, to enter more details about the session.
Step 3
Add People And Time Page
This page consists of a form which gives you the option to invite other members to your session, up next you schedule a time and date when the session will take place, as soon as you create the session, you are directed to the Questionnaire Builder page to add you own questions.
Step 4
Questionnaire Builder Page
This page allows you to build up set of questions you want to ask for the session. On clicking the add questions button, a modal pops up asking you the question details like:
Question Number
Question
Question Type
For certain types of questions you specify a set options you want people to select from. All the questions are displayed in a data table to give the user an idea of the order in which the questions are going to be asked after the meeting starts.
Types of Questions For Direct Decision Making
Various question types to choose from are are -
Wisdom Of Crowd
-In wisdom of crowd round a question is put up, everybody gives their answers and then all the answers are collected.Then we have a voting round, now what happens in a voting round is basically everybody chooses from each others answers, so you pick the answer that you feel best solves the problem and wait for others to choose their answers, once everyone is done we show how many times each answer was chosen so that we get to the best solution for the problem at hand.
Yes Or No
- This type of question allows you to choose from either the yes or no options. These are as simple as the name suggests.
Rating
- This type of question allows you to rate something .Think Amazon Reviews. For example, "How was the food yesterday, rate it from 1 to 5"
Multiple Choice
- This type of question allows you to choose any one option from the options provided. This is suitable for answers which have less than 4 options
Dropdown
- This type of question allows you to choose an option from a number of options provided in a dropdown menu, it is kind of similar to multiple choice. You choose this type of question when the number of options is more than 4.
Checkboxes
- This type of question allows you to choose any number of options from the options provided. You can select all those answers which you find appropriate .
Ranking
- This type of question allows you to drag and arrange the options in a particular order you want to rank them. For example, you could ask team members to rank possible modes of communication.
Upon clicking the submit question button, the question is added in the
Questionnaire Builder
. The question can be edited or deleted from the Questionnaire Builder anytime before the session starts.
When you have added all the questions you want to ask your team members, you click on save and continue button are saves all the questions in the database database and the session creator is directed to
Session Dashboard
page, to view all his sessions.
Step 5
Session Dashboard Page
This page allows you to manage all your sessions, all at the same place.This includes three types of sessions that is my sessions, pending sessions and completed sessions, with a toggle button to switch between card view or table view based on your preference. You can edit a session's questions, delete a session, start a session, join a session, or get a final pdf report. You can also get an AI generated video for the session.
Types of Session on your dashboard
Dashboard consists of
three
types of sessions:
My Sessions
- These type of sessions include all those sessions which have been created by you. It has all the session details along with some buttons -
Start Session
- It becomes active only five minutes before the session's scheduled time, and when the user clicks this, a session is started and user waits for his team members to join.
Edit Question
-It allows you to edit the questions for that session before the session starts.
Delete Session
- this button is used to delete a particular session.
Pending Sessions
- these type of sessions include all those sessions to which you have been invited to. It has all the session details along with two types of buttons -
Join Session
- its activated only after the Session creator starts the Session, this on being clicked directs the user to the waiting area, if the session is started by host, so that they can become part of the question and answer round.
Delete Session
- this button is used to delete a particular session meeting request.
Completed Sessions
- These type of sessions include all the completed sessions, both created by you and joined by you. It has all the session details along with a few special types of buttons -
Generate Final Report
- this upon clicking displays a final report of all the questions that were asked in that session in a table.Thus allowing the user to get a detailed view of each and every question.
Generate PDF
- on being clicked this generates the PDF for that session, which includes all the session details as well as question details of each question that was asked and along with images of the question statistics, the statistics of that particular question, that is form of bar graphs and piecharts, all in the PDF.
Generate Video Report
- this upon clicking gives you an AI generated video , about all the questions that were asked. AWS Polly gives the voice and Viola we have a video explaining the entire question.
Step 6
Waiting For Players To Join Page
When the user clicks the start button or the join button from the session dashboard, they are directed to the waiting area, where they wait for other members to join the session.Only the session creator has the ability to start the session, no other member can do so.The user then chooses his preferred language from the dropdown, as stated before we have a total of 11 languages to choose from.
AWS Translate
Supported Languages
English(English)
Hindi(हिन्दी)
Chinese (中文)
Spanish(español)
Arabic(عربى)
Dutch (Nederlands)
French(français)
German(Deutsche)
Italian(Italiano)
Urdu(اردو)
Japanese(日本人)
This page also has an interesting feature, when the user reaches this page, a dropdown is shown, asking user to select their language,
the game auto detects the language with the help of AI and the use of AWS Translate almost instantly
, this allows the user to answer the questions for the meeting in their own language, thus solving the problem of language differences, there is even a toggle button to switch between their chosen language and default english language.
Before the start of the game the user picks his preferred language.Let us say User A picks "French" The question asked is, "How would you describe the current situation?" which is translated in real time to "Comment décririez-vous la situation actuelle". User A chooses to answer in French, "C'est tres mauvais" which translates to "It is very bad". And he or she waits.
Step 7
After all the players have joined the session, the session creator clicks the start button to start the session.Once the session starts, the questions that were decided by the creator are put forward to all the attendees of the meeting, and they are required to answer the question based on it's respective type.
Question and Answer Round
So the session begins when session creators(let him be called Sarthak) clicks on start session and waits for team members to join, Jane joins, Vaibhav joins, Varun joins, the session length is decided based on number of questions creator has entered for that session. Once everyone has joined Sandy starts the game.
Step 7.1
Enter Answer Page
Once the sessions starts, all the attendees are shown the same question, the picture shows the question 'How is the lockdown treating you?', and the question type is 'Wisdom of Crowd', which means the user can write their own answer. Multi-language support means that irrespective of what language the user answers in it is automatically converted to English.This is the video call equivalent of idea sharing with the added benefit of being anonymous. This helps in overcoming the hereditary bias we inherently have in decision making.
Sarthak answers
"Great".
Jane answers
"Awesome".
Vaibhav answers
"Boring as hell!".
Varun answers
"Nice".
Waiting for players to answer Page
Once user has answered the question by clicking on the submit button, they are directed to waiting area and they wait while other members also answer the same question, and then only you could proceed to to the next step of the game. If the member has already answered the question, a check icon is shown beside their name.
As Sarthak answered
first, he waits for Varun, Jane and Vaibhav to answer.
As Varun answered
, he waits for Vaibhav and Jane to answer
As Vaibhav Answered
, he waits for Jane to answer
And finally Jane answered
The game collects all answers and proceeds to next step of the game.
Step 7.3
Choose answer page
After all members have answered, they are directed to the choose answers page.This page requires user to select the answer which they find the most appropriate from their fellow team member's answers. You are shown all other member's answers as options, while others are shown your answer and not their own answer as options. Why? So that you can't choose your own answer :)
Sarthak is shown all the answers in a jumbled order
Nice
Boring as hell!
Awesome
Sarthak chooses the third answer,
"Boring as hell!"
Jane also chooses,
"Boring as hell!"
Vaibhav chooses
"Nice"
Varun chooses
"Awesome"
In this Round Sarthak chose Vaibhav's answer and his answer "Great" was not chosen by anybody.
Step 7.4
Waiting For Players To Choose Answer Page
Once user has chosen an answer they are directed again to a waiting area where they wait for others.
As Sarthak chooses
first, he waits for Varun, Jane, and Vaibhav to choose their answer.
As Varun chooses
, he waits for Jane and Vaibhav to choose their answer.
As Vaibhav chooses
, he waits for Jane to choose their answer.
And finally Jane chooses
The game collects all the chosen answers as responses and directs the user to display statistics page.
Step 7.5
Display Statistics Page
Once all the users have chosen the answers they feel are right, all the users are shown the results for the question in the form of barchart and piechart. The charts show how many people have chosen a particular answer. The legend for chart shows how many votes each option got.
The legend of both barchart and piechart shows that :
Responses
Votes
Boring as hell!
2
Nice
1
Awesome
1
Great
0
Step 7.6
Waiting For Players To Be Ready For Next Question page
Once user have seen the question statistics they click on ready button, on clicking they are directed to a waiting area again where they wait for others.
Step 7.7
Subsequent Rounds
after all the players have clicked on ready button, they are displayed the next question, and the process goes on in a similar manner.The only difference that the other question types have from wisdom of crowd question type is that they don't get to choose from other member's answers, because they are provided with predefined options to choose from, while all the other rounds remain the same.
As an example , all the user's are shown the next question, "How do you feel about remote work?(MULTIPLE CHOICE)"
As it is a multiple choice question everybody is provided with options to choose from as answer
Options
I love it.
I am getting used to it.
I don't think remote work suits me.
Neutral.
The above table shows an example how options are displayed for each question other than wisdom of crowd question type.
Step 8
Session Dashboard page
After the session has been completed the user is redirected back to session dashboard, and now the session which has been completed, which was earlier in my sessions or pending sessions is now shown in completed sessions.As explained before the user can see the report in Jira itself, get a PDF or get an AI generated video.
Step 9
Final Report Page
This page consists of table which includes all the information about the questions that were asked for a particular session, such as :
Question Number
- stores the number of each question.
Question
- stores the content of each question asked.
Question Type
- stores the type of each question asked.
Options
- stores the option if any for each question asked.
On clicking this field, a modal pops up showing detailed view of options, that is how many votes did each option get.
Display Statistics
- on clicking this button a modal opens up showing the question statistics for answers in the form of pie chart and bar graph.
Sample Video and Pdf Report
View the sample pdf at :
https://wisdom-of-crowd-airtable.s3.amazonaws.com/5f0a492f8c6d1dc9020ba813-pdf.pdf
More About The Libraries Used
AWS Polly
Amazon Polly turns text into lifelike speech, allowing you to create applications that talk. Polly's Text-to-Speech (TTS) service uses advanced deep learning technologies to synthesize natural sounding human speech, this along with ImageMagic in node is used to generate explainatory videos.
View the sample video at :
https://wisdom-of-crowd-airtable.s3.amazonaws.com/5f09f636021cfca73dbf18c5-video.mp4
AWS Translate
Amazon Translate is a neural machine translation service that provides fast, high-quality language translation. Neural machine translation is a form of language translation automation that uses deep learning models to deliver accurate translate. We use translate in 3 ways:-
To translate question from English to other languages
To translate the user's answer back to english
To translate other players answers
C'est tres mauvais, in French is converted to It is very bad
JIRA's Rest API
The Jira REST APIs are used to interact with the Jira Server applications remotely. The Jira Server platform provides the REST API,In this app we use JIRA to save the accountId to MongoDB. We plan to use it create a new issue related to question giving the user the power to add comments.
Know more about our app
Checkout the website to see more features-
Wisdom of crowd features
Roadmap
Integrate a chat bot to do all of this process hands free.
Make the game ui more interactive
Make a mobile app depicting the same
Test our app with a company
Contact
Sarthak Arora -
[email protected]
Varun Ramnani -
[email protected]
Vaibhav Garg -
[email protected]
Youtube link
Wisdom of Crowd
How I built it
This game was built using Atlassian's Connect framework and Atlaskit UI, MongoDB, React, Redux, Express, Node and Redis Streams and Data Structures, Aws Translate, S3 and Polly.
Atlaskit Ui:
This is used to design the ui components in React to make the App more attractive and visually impressive.
Atlassian's Connect Framework:
It acts as an bridge between the react app and JIRA, we use Webpack to bundle everything in the form of a module.
MongoDB:
This is used to store user info, and questions in the game, addtionally it stores data about the previous games
Node:
NodeJS works as backend of the application the players communicate to the Redis streams by the means of POST Requests.
Aws Translate:
This is used for real time language translation, thus allowing user for cross language communication.
Aws S3:
This is used for data accessibility and storage, for images and pdfs generated also the videos are stored in this way.
Aws Polly:
This library along with nodejs is used for text to speech conversion and AI videoo generation.
Challenges I ran into
While setting up Connect Framework and using Atlaskit ui components, then there was the challenge of setting up the app with Jira and using AWS translate and AWS polly and S3 bucket along with some challenges with redis streams.
Accomplishments that I'm proud of
We were able to make a decent enough App which can be efficiently used by various companies as a solution to team voting and for instant accessibility of data as well as solving the problem of cross-language communication.
What I learned
Using typescript efficiently
Using Jira and Atlaskit ui properly
Implementing Model-View-Controller pattern in backend
Using JWT authentication in NodeJs
Setting MongoDB Atlas
Defining Complex Schema's in MongoDb
How to setup a full stack application using the MERN stack
How to set up a connect app
Setting up Redis on our machines
Using Redis Streams
Using Lists in Redis
Using AWS, that it's S3 bucket, Translate and Polly.
Wisdom Of Crowd Round French Uncut
Wisdom of Crowd French Uncut
What's next for Wisdom of Crowd
Integrate a chatbot to do all of this process hands free.
Make the ui more interactive
Built With
amazon-web-services
jira
machine-learning
mongodb
node.js
pdfkit
react
redis
redux
typescript
Try it out
wisdom-of-crowd-jira.herokuapp.com | JIRA's Wisdom of Crowd | An Artificial Intelligence powered real time multilingual team voting application. | ['Sarthak Arora', 'VAibhav GArg', 'Varun Ramnani'] | [] | ['amazon-web-services', 'jira', 'machine-learning', 'mongodb', 'node.js', 'pdfkit', 'react', 'redis', 'redux', 'typescript'] | 118 |
10,045 | https://devpost.com/software/mendelfields | Inspiration
Impact and Urgency are widely use to define priority. JSD Automation provides a way to implement this, but only works on creation and not after.
What it does
Changes Priority based on Urgency and Impact
How I built it
We create a trigger that compares values of Impact and Urgency to change the value of Priority
Challenges I ran into
As Forge can only display views in the issue field, we can't make a UI to configure the matrix
Accomplishments that I'm proud of
A simple but powerful solution for an ITIL everyday problem
What I learned
To use triggers and API
What's next for MendelFields
Add a gadget to see the matrix and tickets in each cell.
Add a UI to configure the matrix
Built With
api
atlassian
trigger-forge | MendelFields | It's widely use to define an incident priority base on the value of impact and urgency. Using triggers, we check of any change to the fields Impact and Urgency, and change priority accordingly. | ['Daniel Añez', 'Marcelo Mella', 'Miguel Obando'] | [] | ['api', 'atlassian', 'trigger-forge'] | 119 |
10,045 | https://devpost.com/software/multiple-filters-chart-gadget-cloud | Multiple Filters Statistic Bar Chart Gadget (Horizontal)
Multiple Filters Statistic Bar Chart Gadget (Vertical)
Multiple Filters Statistic Line Chart Gadget
Multiple Filters Pie Chart Gadget
Inspiration
We have a Multiple Filters Chart Gadget server edition and we have requests to port it for Jira Cloud.
What it does
Combine multiple filters into a single chart or data table, grouped by the selected statistic type, and calculated based on issue count, number fields or time fields.
How I built it
Using atlassian-connect-spring-boot
What's next for Multiple Filters Chart Gadget Cloud
Adding charts plotted against selected date fields, which are available in the server edition.
Built With
atlassian-connect-spring-boot
java
javascript
jira | Multiple Filters Chart Gadget Cloud | Combine multiple filters into a single chart or data table. Choose from 3 types of chart, bar, line or pie. | ['Angela Teo'] | [] | ['atlassian-connect-spring-boot', 'java', 'javascript', 'jira'] | 120 |
10,045 | https://devpost.com/software/azure-devops-links-for-confluence | Display rich information about Features, tasks from Azure DevOps
Display rich information about Epics from Azure DevOps
Display rich information about work items from Azure DevOps
Inspiration
Tired of jumping between Atlassian Confluence and Azure DevOps work items? With Azure DevOps links for Confluence you can unfurl Azure DevOps work items and other links in useful information-rich content.
What it does
Bring up-to-date information about Azure DevOps entities into Confluence
How I built it
We built it as Confluence macros.
Challenges I ran into
Our App seemed pretty simple and only a couple of day of work, how wrong we were.
We had a lot of difficulties with macros resizing according to the content
unit and integration testing our dependency-rich App
Accomplishments that I'm proud of
The App itself
What's next for Azure DevOps links for Confluence
support more links
support Confluence Server
Built With
amazon-web-services
atlassian
azure-devops
react
serverless
typescript
Try it out
moveworkforward.atlassian.net | Azure DevOps links for Confluence | Bring Azure DevOps information directly into your Confluence content. | ['Move Work Forward'] | [] | ['amazon-web-services', 'atlassian', 'azure-devops', 'react', 'serverless', 'typescript'] | 121 |
10,045 | https://devpost.com/software/three-dimensional-date-gadget-for-jira-cloud | Configuration
Three Dimensional Monthly Gadget
We have a Three Dimensional Date Gadget server edition and want to port it for Jira Cloud.
Issues have to be retrieved via REST api and processing of data on the frontend, unlike the server edition.
Built With
atlassian
connect
express.js | Three Dimensional Date Gadget for Jira Cloud | Visualise issues distribution across the months on a table based on your selected field and another date field. | ['Xin Fang Chia'] | [] | ['atlassian', 'connect', 'express.js'] | 122 |
10,045 | https://devpost.com/software/atlassian-jira-online-learning-platform | Atlassian JIRA Online Learning Platform
* Inspiration/Problem Statement *
Given the recent global COVID-19 pandemic, unemployment is at an all time high. A lot of people have either lost their jobs or are working with reduced works hours and pay cuts etc. Many students too around the world will have to defer their admission by a year or have to complete majority of their coursework virtually. This problem has lead to an opportunity to completely transform how people learn. There is an urgent and high demand to upskill and retrain in new job areas where it is high in demand. There is a need for unconventional, accessible and affordable learning platforms using VR. But this learning transformation faces a challenge to safeguard the learners from scammers. A lot of new users who have never previously been active learners online will change their style of learning and are more prone to getting scammed and have a bad experience. Since the COVID-19 pandemic, there are a lot of free courses on demand but many apart from large corporations are scams. We propose to build a platform to only onboard verified instructors with qualifications.
Overview
The goal of the platform is to give jobseekers a chance to have access to a well qualified and verified instructors who is competent to train them remotely, with flexibility and accessibility available. We do not strive to be another traditonal university but rather a hybrid of community college and university, where students are coddled to a certain extent but take their own responsibility for their work by reminding them about assignments and due dates in emails weekly and what questions can be asked. There is also a live webinar weekly with web accessibility for different abilities.
How it works
A trainer can upload his/her video by creating an account and pay for the content to be uploaded to students; however this is open source and free for students. A student will search the course he or she wants to learn and enroll into the course. The payment will be done through Paypal, credit card or blockchain coins Bitcoin and Ethereum. A preview of the course for students is provided to find out if the course is for them or not, and whether it has proper web accessibility requirements met and the qualifications verified.
How I built it
Atlassian Confluence Build Connect is used with the add-on library atlassian-connect-express from the JIRA documentations/npm install and written in Javascript with some CSS. The back-end uses some Docker and MongoDB with some internal APIs used. In developing this application, Node.js was the primary source and Express.js was the secondary source for the application.
Challenges I ran into
Unreliable team members and difficulty in communication
Accomplishments that I'm proud of/What I learned
Learning new skills and understanding different
What's next for Atlassian JIRA Online Learning Platform
Anyone can contribute with instructions on the contributing.md page of the GitHub repository
Built With
api
atlassian
express.js
javascript
mongodb
node.js
Try it out
github.com | Atlassian JIRA Online Learning Platform | This website is for people want to upskill or re-train for a new job and a different teaching platform usage | [] | [] | ['api', 'atlassian', 'express.js', 'javascript', 'mongodb', 'node.js'] | 123 |
10,045 | https://devpost.com/software/jra-in-aws-k8s-automation | Inspiration
This will deploy everything automatically through aws api, will create a 'Cloud Formation' cluster, you will be able to do kubectl from the system you are installing. This will also create two ECR registry, one for Jira and one for database.
What it does
Deploy Jira in aws EKS kubernetes in a automated fashion.
How I built it
You can do this with a aws free tier account, login and go to IAM and create a user with "AdministerAccess" privilege and obtain AWS Access Key ID AWS Secret Access Key Everything else is automated, even databe connection.
Challenges I ran into
Tried Mysql, but didn't work. May be I was doing something wrong :D
Accomplishments that I'm proud of
Its completely automated and anyone can install Jira without the help of solution partners
What I learned
Adopt Jira docker image to use external databse
What's next for Jira in aws k8s automation
Would like to integrate with aws aelxa, then when we say "create a Jira instance", it should spin up a new Jira and kuberentes cluster. Also can integrate confluence, bitbucket etc.
Built With
amazon-web-services
docker
jira
kubernetes
postgresql
Try it out
github.com | Jira in aws k8s automation | Deploy Jira in aws EKS kubernetes in a automated fashion. Postgresql is also integrated as environment variable and you don't need to configure it. Will customize docker image for adding db driver. | ['Kamal Kailasa Babu'] | [] | ['amazon-web-services', 'docker', 'jira', 'kubernetes', 'postgresql'] | 124 |
10,045 | https://devpost.com/software/jira-project | Printed version
List of main features of the tool
Newspaper settings on Jira
Printed version
Viewing the newspaper on the phone
Newspaper for sprint "MVP - Search for cars"
Full second page
Inspiration
Stakeholders want to know about the latest development of their projects, but the Product Owner not always have time to contact each of them, or to write descriptions for the sprint. Some stakeholders are not comfortable with the user story format (As a user I want to... so that...), although it contains the important facts why the story should be implemented. This inspired creating a tool that could generate content focused on stakeholders, highlighting what they have requested and which benefit they will get, in a visual that imitates a newspaper to be simpler and not focused on tech - without wasting the Product Owner's time. This format seems to be also good for printing and putting it on wall, which can bring
visibility in an "organic" way
.
What it does
Using Machine Learning, the tool extracts roles, requests and benefits from user stories and writes in a newspaper-like way a page that shows-off why the sprint is important, who it is helping, and what we can expect in the future. It works for next-gen projects that has stories created using the agile story template (As a user I want... so that...).
How I built it
The plugin was written in Javascript and used components from Atlaskit for React. The back-end solution was developed using the Atlassian Connect Spring Boot framework, the Jira REST API, and Google AutoML, using Java.
Challenges I ran into
Finding the correct place to create the add-on was harder than I thought.
I started using Google AutoML via REST with local authentication, but on the last minutes I had to change to use their own libraries when I had to deploy it on a server.
Accomplishments that I'm proud of
The integration with Jira works smoothly.
Creating and using a ML model.
Testing the add-on in different Jira accounts brought extra satisfaction :)
What I learned
Integration with the Jira Platform
More knowledge on security and JWT
What's next for Jira Project
Improving layout and publishing it on the Atlassian Marketplace
Built With
atlaskit
atlassian-connect
google-auto-ml
java
javascript
jira | SprintNews | A tool that shows the benefits that sprints bring to stakeholders by inspecting stories and generating content tailored to them, in an easy-to-read format. | ['Danilo Teodoro'] | [] | ['atlaskit', 'atlassian-connect', 'google-auto-ml', 'java', 'javascript', 'jira'] | 125 |
10,045 | https://devpost.com/software/banners-for-confluence-cloud | Different style counter banners
Different coloured icon banners
Different coloured counter banners
While exploring Forge, we saw a possibility to make Confluence more colourful and lively. We thought it will be good if we can use it for our apps user guides which are hosted in Atlassian Cloud (
https://akeles.jira.com/wiki
)
We are very pleased with our design which can scale nicely on different screens (mobile/ipad/laptop/monitor)
The original name of the macro is called Headings, but we decided to rename it because it will be easier for users to select the macros.
It is important that the icons have a common design style. We were lucky to find attractive SVG linecons provided by designmodo.com
https://designmodo.com/linecons-free/
Built With
atlassian-forge
node.js | Banners for Confluence Cloud | To simplify the content creation process for users without the need to create and upload graphics with image editors.Users can add heading banners quickly within Confluence with available options. | ['Stella Wong', 'Hua Soon Sim'] | [] | ['atlassian-forge', 'node.js'] | 126 |
10,045 | https://devpost.com/software/related-tickets-for-jira | The issue view with Related Tickets for Jira
The table for related tickets
We have been using Jira Service Desk Cloud as a Service Desk for our Marketplace apps.
While exploring Atlassian Forge, the idea came about to display other tickets from the same customer when viewing a support ticket in agent view.
Previously we have to open a new tab and execute a search manually. With this Forge app, the information is displayed neatly in a table automatically.
Now my team members can conveniently identify
Past tickets
Duplicate tickets
Related tickets
This way, we can have a better picture and address the tickets in personalised manner.
We think Atlassian Forge offers new possibilities. Even with Atlassian Forge beta, it is easy to create functional apps in Jira Cloud without the need to host any servers.
Currently, we hard-coded the project key to limit the feature specifically for our Jira Service Desk project. We are hoping for new improvements so that it is possible to configure the display settings for various projects
Built With
atlassian-forge
node.js | Related Tickets for Jira | By listing related tickets raised by the same person within the same service desk, the Service Desk agents can understand the customer better and be well-positioned to resolve the ticket. | ['Victor Tay'] | [] | ['atlassian-forge', 'node.js'] | 127 |
10,045 | https://devpost.com/software/tone-analyser-for-confluence-cloud | Inspiration
We've written our fair share of documentation, internal, external and everywhere between those. We've experienced first hand that when you write technical notes or documentation at the end of a long day, no matter how optimistic you are, things might get a little cynical and possibly negative. Obviously, this is not on purpose, but it will be perceived as negative by the reader. In our current team, a quick message or comment pointing out negative sentiment is usually enough, but ideally we would be able to immediately identify any sort of negative sentiment. That's why we built Tone Analyser for Confluence, to help us write positive, constructive content in Confluence.
What it does
Tone Analyser uses Natural Language Processing (NLP) and Machine Learning (ML) to analyse the sentiment of Confluence Pages. After publishing a page, Tone Analyser will start analysing your document and in mere seconds you will be informed about the sentiment via the Confluence byline section, at the top of the page using easy to understand and clear communication.
How we built it
After researching sentiment analysis and NLP, we came up with several visual prototypes to find the best way to visualize sentiment. Using Atlassian Connect, a sentiment API and some of our own frameworks we prototyped a total of 2 concepts, of which we implemented one in the final version.
Challenges we ran into
Sentiment can be calculated in multiple ways, each of which comes with a different sort of outcome in terms of value output. We've prototyped several options before we found the best way to visualize sentiment.
Accomplishments that we're proud of
In terms of team accomplishment, we're most proud of the fact we were able to release this app along with other apps, regardless of the time restriction and the need to make major changes to the way the app works. Most of all, the app is very much in line with our idea that plugins should be simple: easy to use, little explanation needed and non-obtrusive. Ironically enough, the simpler the app for users, the more difficult it becomes to build it.
What we learned
The importance of templates, frameworks and a clear goal has proven to be even more important when time is of the essence. In terms of machine learning and NLP, we've learned loads about types of sentiment, ways to analyse text and how people interpret sentiment..
What's next for Tone Analyser for Confluence Cloud
Although figuring out the sentiment of Confluence pages is a great help for people who write, we have about a dozen ideas on how we can improve content writing on Confluence using machine learning and NLP that we are excited to add to the application. | Tone Analyser for Confluence Cloud | Confluence pages can sometimes turn to negative or cynical written documents. Tone Analyser is a small app that helps to remind you to keep things positive by applying sentiment analysis. | ['Jari Sanders', 'Remie Bolte', 'Jonas Hallensleben', 'Rene Slump', 'Tamara Bazko'] | [] | [] | 128 |
10,045 | https://devpost.com/software/figma-for-jira-pro | Figma for Jira PRO - Vector Preview
Inspiration
As small multi-disciplinary design and development team, we have tried many of the existing tools that were available that promised to bridge the gap between design, development and product. Unfortunately, none of them actually did. We were limited by the lack of basic functionality and a complex licensing issues that made it very difficult to work with. For Figma for Jira PRO, we aimed to build an app that would allow anyone in a Jira project to work with Figma designs that would
actually
help and even encourage close collaboration between designers and developers.
What it does
Figma for Jira PRO allows Jira users to attach Figma designs right into Jira issues, whether that's a single frame of a webpage, or each of the buttons that are part of your design system. All you need to do is to right click your Figma frame, press Copy Link and paste in into the Figma for Jira PRO field on your Jira issue and click Add. Every time you open the Jira issue with the Figma frame attached to it, the app uses the official Figma API to fetch the latest version of your design and allow you to preview it as a vector file in a full screen window. Thanks to the vector file, you can preview designs at any zoom level you wish.
Thanks to the advanced Admin section of the app, Jira administrators remain fully in control of the access keys, Figma files and are able to quickly troubleshoot any connectivity issues. This makes the app a true enterprise ready application.
How we built it
Thanks to our growing library of templates and frameworks for Atlassian apps, we have been able to build the app in iterative fashion.
Challenges we ran into
The easier you make the user experience, the more difficult it is to build it, especially if you want to offer a complete offering that is not limited to embedding a public URL. This challenged us big time but thanks to quick feedback loops and early prototyping we've managed to accomplish a result that has proven to be of great help for some of our early customers.
Accomplishments that we're proud of
With Figma for Jira PRO we have been able to build something that not only enables us to collaborate better and faster, but also others. It's very inspiring and almost addictive to build something and find out countless of other teams were in need of what you build.
What we learned
By using some of the early prototypes ourselves in our own team we have been able to iterate early and often, and create something that not only has great features but is also a breeze to use. If an app does not actually improve a process, it's useless. We've learned that there's great demand for apps that exceed expectations.
What's next for Figma for Jira PRO
We are continuing to invest in the app to build the best vehicle for design and development collaboration for Jira and Figma.
Built With
collabsoft-ui-kit
connect
figma
jira
Try it out
marketplace.atlassian.com | Figma for Jira PRO | Allow real-time collaboration between Designers and Developers without limitations. | ['Remie Bolte', 'Jonas Hallensleben', 'Jari Sanders', 'Tamara Bazko'] | [] | ['collabsoft-ui-kit', 'connect', 'figma', 'jira'] | 129 |
10,045 | https://devpost.com/software/figma-for-confluence | Inspiration
As small multi-disciplinary design and development team, we have tried many of the existing tools that were available that promised to bridge the gap between design, development and product. Unfortunately, none of them actually did. After building our initial Figma for Confluence app that allowed users to embed public files only, we have been inspired by our users to build everything from the ground up and build a brand new app that offers designers and PMs the ability to embed real-time frames from both public and private Figma files for documentation, design systems, handovers and presentations in Confluence.
What it does
Figma for Confluence allows Figma users to embed files and specific frames of their Figma files right into their documentation. Thanks to 4 different scaling options, users are in full control of how their files are shown and integrated into the document. The advanced admin section of the app gives Jira Administrators full control of access tokens and which files are embedded in Confluence.
How we built it
Thanks to our growing library of templates and frameworks for Atlassian apps, we have been able to build the app in iterative fashion, using the feedback and learnings from our other app Figma for Conluence LITE.
Challenges we ran into
Scaling things can be difficult, scaling multiple things proportionally and relative to each other is even more difficult. What was even more difficult is the fact that we wanted to support as many different use cases as possible.
When documenting a Design system, having a fixed macro container with fixed size with each of the elements displayed at 100% makes most sense, but in other cases, adapting the size of the design to the macro by zooming in or out is a better option. We've listened closely to our potential users to support as many use cases as possible while keeping the interface as simple as possible.
Accomplishments that we are proud of
With Figma for Confluence we have really gone the extra mile in terms of user centered design. We have not only focussed on the low hanging fruits but researched the actual needs and benefits Figma users are expecting, which proved to be worth the investment.
What we learned
As part of our user research and iterative continuous design and development sprints we have been in touch with a large number of potential users that helped us a lot with figuring out their needs and what's important.
What's next for Figma for Confluence
We're already working on the next version of the app to offer even more tools for designers using Figma and Confluence: we are in this for the long run. Next to Confluence, we have also built Figma for Jira PRO, which will enable an even more complete and integrated experience for our users.
Built With
figma
Try it out
marketplace.atlassian.com | Figma for Confluence | Combine Figma and Confluence for effortless, up-to-date design documentation and handover documents, with infinite pixel perfect vector scaling options. Supports private and public files! | ['Jari Sanders', 'Remie Bolte', 'Tamara Bazko', 'Jonas Hallensleben'] | [] | ['figma'] | 130 |
10,045 | https://devpost.com/software/wordart-for-confluence | Inspiration
What started out as a "imagine if Confluence had..." joke turned into something we could not stop playing with. Although the new Confluence editor is super versatile, sometimes you just need to add some extra flair onto a page, what better way to do that using WordArt?
What it does
WordArt for Confluence initially only did one thing: alllow you to add WordArt to your document. But we did not stop there, we added the ability to make it
blink
.
How we built it
Thanks to frameworks we created while working on other apps, we were able to create the app 100% based on components from existing Collabsoft apps.
Challenges we ran into
We realized very well that WordArt is not something you can take lightly, it needed to be perfect, which was a challenge at times.
Accomplishments that we're proud of
We feel like we've created the only thing that was still missing from Confluence.
What we learned
During the process, we've been reminded how awesome WordArt is, and how we missed it in our documentation flow.
What's next for WordArt for Confluence
For now, not much but we are very interested to hear your feedback and suggestions.
Built With
collabsoft-ui-kit
connect | WordArt for Confluence | The one thing that was still missing from Confluence Cloud: WordArt!Spice up your documents and make an impact with the 30 original WordArt styles from back in the day. Scales infinitely. | ['Jari Sanders', 'Remie Bolte', 'Jonas Hallensleben', 'Tamara Bazko'] | [] | ['collabsoft-ui-kit', 'connect'] | 131 |
10,045 | https://devpost.com/software/integration-with-connectwise-manage-for-confluence-cloud | Setup UI for API credentials
Mapping a company record to a Confluence space and the option to create a content parent page "CW Manage Integration"
The templated parent page renders the linked company's details and allows the user to create pages based on Connectwise content with a click
A page example based on selected configuration type with the 'Refresh CW content' to pull the latest version
Inspiration
A few years ago I was working with a team of Java developers to deliver a
Confluence Server add-on
that allows IT service providers to integrate
ConnectWise Manage
with Confluence. Since it took a lot of effort we didn't get to move it to Confluence Cloud back then.
Now to build something similar for Confluence Cloud (with less features) without any infrastructure is quite tempting. Forge UI looked good and the Atlassian Forge concept made a lot of sense to me.
What it does
The app is an integration with
ConnectWise Manage
so e.g. IT service providers can compile technical site documentation in Confluence Cloud instances, based on so called 'Configurations' stored in ConnectWise Manage.
Confluence keeps track of changes (page history) and allows to configuration data from put multiple configuration types on the same page which makes it easy to gain an overview of all the tech. details captured.
How I built it
After studying a few Forge example apps for Confluence and experimenting with tutorials, I've grabbed a few building blocks and started hacking it together.
I'm using the ConnectWise Rest API endpoints and ConnectWise API Member authentication.
Challenges I ran into
Limited support for UI elements. Lack of knowledge of the tech. stack (React, TypeScript, Hooks). I was new to the ConnectWise Rest API and the Forge Javascript API.
I always find Confluence most useful when I can search for content keywords. So I decided to create pages rather than just render the external content inside a Confluence page.
Accomplishments that I'm proud of
I've manage to build some 'templated' content (not using Confluence templates) so the user can create pages with a few clicks without having to place macros manually.
The setup and settings screens have a nice flow and hopefully are intuitive to use.
Also, the refresh button allows the user to pull a new version (using stored content properties).
What I learned
I've learned quite a bit about React, TypeScript, Hooks
What's next for Integration with ConnectWise Manage for Confluence Cloud
I still got a fair backlog of improvements. However, I'm most keen to hear some feedback from potential users. Would be really nice if we can offer the app on the Atlassian Marketplace as well.
Built With
atlassian
forge
javascript | Integration with ConnectWise Manage for Confluence Cloud | Compile technical site documentation based on ConnectWise Manage configurations in a Confluence Cloud space and reference it from your Confluence knowledge base. | ['Thomas Berger'] | [] | ['atlassian', 'forge', 'javascript'] | 132 |
10,045 | https://devpost.com/software/latex-for-confluence | In-line and Block LaTeX equation examples
Extra features examples (Styling and LaTeX packages)
Inspiration
Content formatting and management are increasing requirements within the Confluence space. There are lots of great options currently available on DC and Server in the Marketplace, whether it's a solution that offers a suite of functionality as a bundle or one that offer a single individual functionality (the former are typically more expensive). The availability of these solutions however are less abundant on Cloud, understandable as Confluence Cloud is still growing. We therefore wanted to create a solution on Cloud that allows users to manage their content better and improve engagement.
One of these is LaTeX for Confluence, it allows the user to convert and display LaTeX mathematical formulas on Confluence pages.
What it does
LaTeX Macro converts inline and block LaTeX mathematical formulas into HTML so they can be displayed on a Confluence page.
How I built it
We initially built a base Confluence Cloud App before building the macros on top. These in general took a few days due to its complex functionalities. We also followed the provided Atlassian documentation
https://developer.atlassian.com/cloud/confluence/getting-started/#step-4--create-a-basic-app
.
Challenges I ran into
Being new to Atlassian cloud it was a challenge to learn what was possible with the API and how to achieve certain tasks. One of the issues faced was how to dynamically change the size of the parent iframe after the page was rendered. This was an issue because the LaTeX library parses text in the body of the macro after Confluence mechanisms determine the iframe size. The LaTeX library applies CSS and prettifies the contained text which in many cases enlarges the contained content which in turn forces the parent iframe to show scroll bars. This was mitigated by calling the auto resize function on the iframe to calculate a new size after the content has been prettyfied.
What I learned
How Atlassian's connect approach to add-on development works. Learning how to navigate it's limitations and API.
What's next for LaTeX for Confluence
Evaluating the performance once released and future feature updates to provide value to users.
Built With
connect
Try it out
marketplace.atlassian.com | LaTeX for Confluence | Convert and display LaTeX mathematical formulas on Confluence pages using the LaTex Macro | ['christo-m', 'Andrea Rosati', 'Deborah Scott', 'Dylan Lindsay', 'Kankemwa Ishaku', 'Orah Apps Ltd'] | [] | ['connect'] | 133 |
10,045 | https://devpost.com/software/microsoft-teams-confluence-connector | Connect Confluence with Microsoft Teams
Watch content in Confluence in Microsoft Teams
Unfurl links and search content from Microsoft Teams
Filter down the noise.
Inspiration
We completely rewrote our old app. We developed a Microsoft Teams bot, completely new UI and infra.
What it does
Microsoft Teams Confluence Connector integrates Microsoft Teams with Confluence and helps teams and individuals to increase team visibility and openness.
How I built it
We built it with Serverless Framework on AWS, Atlassian Connect Framework to integrate with Confluence Cloud.
Challenges I ran into
Multiple:
App submission process with Microsoft
Using poorly or undocumented APIs from Microsoft and Atlassian
Accomplishments that I'm proud of
The App and the Bot are released!
What I learned
What's next for Microsoft Teams Confluence Connector
Multiple enhancements:
scheduled reports
alerts
content embedding in Microsoft Teams
bi-directional integration between Microsoft Teams and Confluence
Built With
amazon-web-services
atlassian
bot
botframework
confluence
microsoft-teams
react
serverless
typescript
Try it out
marketplace.atlassian.com
moveworkforward.atlassian.net | Microsoft Teams Confluence Connector | Connect your Confluence with Microsoft Teams to increate team transparency and openness. Boost that dev speed | ['Move Work Forward'] | [] | ['amazon-web-services', 'atlassian', 'bot', 'botframework', 'confluence', 'microsoft-teams', 'react', 'serverless', 'typescript'] | 134 |
10,045 | https://devpost.com/software/image-magnet | Macro Configuration
Image Magnet
Alt Text if image load fails
Inspiration
The primary driver for this project is one of my personal gripes with the new confluence editor. In my workflow I need to include a lot of images from the web in confluence. The ability to import images from URL was available in the old editor but it is missing in the new editor. I did some digging in Confluence's own jira project and I see the same issue with around 100 votes. Also a related feature is resizing the image with over 250 votes. I wanted to combine these 2 features in a Confluence macro built on forge.
https://jira.atlassian.com/browse/CONFCLOUD-65749
(
+98 upvotes
)
https://jira.atlassian.com/browse/CONFCLOUD-67554
(
+257 upvotes
)
What it does
Imports image from a URL
Adds alt-text
Resizes the image
How I built it
I built a confluence macro with forge to get the Image URL, Alt Text & Sizes.
I built a Heroku API to resize the image and return the new URL back to Confluence for loading the resized image.
Challenges I ran into
There are no validations available yet for UI components. The experience would be a lot smoother if we have them.
Accomplishments that I'm proud of
I was able to fix an issue I personally faced with Confluence and being able to help about 300 upvoters in the process.
What I learned
Forge can add huge value to Atlassian products. Even though it is not fully baked yet I see the potential. Users like myself can fix bugs/ add their own features using forge apps without relying/waiting for Atlassian team work.
What's next for Image Magnet
I will try and add more controls to the image manipulation.
Built With
confluence
forge
heroku
node.js | Image Magnet | Imports image from a given URL and resizes | ['Uday P'] | [] | ['confluence', 'forge', 'heroku', 'node.js'] | 135 |
10,045 | https://devpost.com/software/flipchart | Sample diagram created in Flipchart
Prepared jira workflow - another sample in Flipchart
How to add and use the Flipchart - another sample in Flipchart
Flipchart basic architecture - another sample in Flipchart
Inspiration
Our work is a place where we like to meet and discuss our ideas. There is always a board available for us to model all the components of the project we work on. Coronavirus changed everything. There was no other way than to work remotely. We started meeting online. Only then did we realize that we needed some new opportunities to share our ideas. We needed a tool for simultaneous modelling and designing a project so that we would have a visible effect later. However, we didn't want to change the tools that we are so familiar with, for example Jira, Confluence, Bitbucket.
What it does
Flipchart enables you to model diagrams on the page published in Confluence. Thanks to that, anyone who has access to a page can cooperate to design the desired content. After a user creates a meeting note and adds a flipchart macro to it, other users can edit the content live.
How we built it
We used Atlassian Connect to create Flipchart macro. We learnt how to use NodeJs and JointJs. We had to handle users' connections and communication between them. The application is based on WebSockets communication for the exchange of information between the author of the modifications and the meeting subscribers. We used the observer design pattern in connection with event sourcing architecture. Unlike Forge, Atlassian Connect could handle this. Forge doesn't support dynamic content macros which we used to show and edit diagrams.
Challenges we ran into
The biggest challenge was time pressure since we joined hackathon 2 weeks before the deadline. Additionally, we had to find a solution how to disable concurrent modification of the same item of the diagram. In this way, the users wouldn't affect the cohesion of the diagram data. Another issue to work on was the creation of events which would recreate the diagram for new participants of the meeting.
Accomplishments that we're proud of
We succeeded in delivering the tool based on the engine which coordinates the work of the concurrent users. We also managed to deliver a basic functionality which helps to create diagrams.
What's next for Flipchart
The macro we created can be a starting point for new functionalities used to create advanced diagrams. We also want to improve the user's interface. Should you have any feedback or suggestions, feel free to contact us.
Flipchart will eventually be part of Atlassian Marketplace.
Built With
atlassian-connect
confluence
heroku
javascript
jointjs
node.js
websockets
Try it out
salty-castle-80074.herokuapp.com
flipcharts.atlassian.net | Flipchart for Confluence | Work together to create diagrams in Confluence. Flipchart allows simultaneous work on the diagram by several people at the same time, using the same page. Sounds impossible? Give it a go! | ['Paweł Ciereszyński', 'Artur Gałązka'] | [] | ['atlassian-connect', 'confluence', 'heroku', 'javascript', 'jointjs', 'node.js', 'websockets'] | 136 |
10,045 | https://devpost.com/software/book-club | Logo
Gadget screenshot: Recommended updates
Inspiration
Different sources in Atlassian products, such as the activity stream, in-app notifications, and email notifications, inundate users with updates on activities and information. The goal of these features is to provide an easy way for users to stay informed and help them be more efficient and effective. Users commonly complain about these features though and they think the features are not as helpful as they could be.
Common complaints
Too much information – Users can’t find the information they care about quickly and they don’t have the time or desire to sift through the information. This causes users to miss valuable information and be less effective at their job.
Too little information – Users know that there are activities happening that they want to know about, but the product isn’t telling them the activities occurred. This is usually due to a product configuration problem. The system may have been configured to provide minimal updates to users to prevent the too much information problem. Users may or may not have sufficient rights to change the configuration.
Too difficult to configure – These users know there is a way to change or customize the system’s configuration to provide more of the information they need and less of the information they don’t want Most users don’t go through the trouble though because changing the configuration is too difficult. It would require significant effort to configure the system and keep the configuration correct for their changing needs. They may not even have sufficient privileges to change some of the settings themselves. Also, the rigid configuration options would still cause them to get too much or too little information.
One of the key benefits of widely using Atlassian products across an organization is users can find information relevant to their work even when they’re not directly involved with it. The rate information changes and the amount of information available in Atlassian products increases exponentially as usage of the products increases. Users need a solution to the issues with the current features so they can stay informed about the information important to them despite information rapidly changing and growing. Well informed users perform better and make better decisions.
Our goal is to provide an easy way for users to stay informed and up-to-date on things related to their work without requiring them to spend a lot of time configuring a system or searching for information that may or may not exist. A solution that understands their unique needs. Also, a solution that understands their needs change over time.
What it does
Smart Stream is a dashboard gadget allows you to stay up-to-date and informed about topics related to you. It requires minimal effort to use, personalizes the information to you, and adapts quickly to your changing needs. It overcomes the challenges of the rigid built-in activity stream.
The gadget is an AI powered activity stream. It looks at all the information you would see in your unfiltered activity stream and shows you a refined list of activities it is recommends you review. The recommendations are based on what the system has learned you are interested in. It is constantly learning and improving its recommendations. The recommended list hides all the extra noise while allowing you to see activity for things you didn't even know you needed to watch. No AI is perfect though, so the gadget also provides access to the unfiltered activity stream, so you never miss anything.
Smart Stream starts learning from the first time the gadget is added to your dashboard. The system creates a baseline for your interests by recording the issues you are watching when the gadget is added. It uses the information in the Summary and Description fields of those issues to match activities to your interests. For example, if you're watching issues that mention "shopping cart" in Description, Smart Stream will recommend that you review activities that occur on any issues with "shopping cart" in the Description or Summary.
You can improve your recommendations by telling the system what you want to see. Each activity has an option to "see more" or "see less" activities for issues similar to it. For example, if you see an activity in your unfiltered stream that is not in your recommendations, you can select to "see more activities like this" and in the future the system will show in your recommendations activities for the issue and issues with similar subjects in the Summary in Description.
How I built it
The Jira app (gadget) was built with Atlassian Connect for Node.js Express. I wanted to be able to use new AtlasKit components so I integrated a React.js webapp on top of Express. There wasn't a whole lof of "new" UI to create because we felt that the Jira Activity gadget patterns already worked so well.
The "smarts" of the application was in AWS. Data storage in DynamoDB, gets and sets of information with Lambdas triggered by API gateway. Basic gets & sets of information was written in Javascript (node) but the machine learning part of it was in Python using Pandas for data preparation and manipulation. Used SciKit Learn to "make the recommendations".
Data storage is GDPR compliant and no intellectual property left Jira. Meaning, I did not store any details about Jira issues.
I would've gone all AWS but I had issues deploying the Jira app itself with Beanstalk so I went the Heroku route.
Challenges I ran into
Atlassian products have a very versatile set of users. There is no one way a company or users use the product. It is difficult to know if the solution will work for most users. You can't judge it based on how you, your team, or even your company use the product. We tackled this challenge by focusing our product on the needs of engineers and talking to engineers from several companies to understand their challenges.
Machine learning is a big part of how the solution determines what a user sees in their recommended feed. There isn't a simple machine learning algorithm that accounts for all the factors that influence what a user wants though. Any changes to the algorithm have to be tested to ensure they provided the expected improvement. It is challenging to have the right data for testing and to validate the algorithm is working. We limited the algorithm to finding related items items based on issue content to minimize this challenge for the hackathon.
Accomplishments that I'm proud of
This is my first machine learning application I've ever built
This is my first Atlassian app I've ever built
What I learned
There are many types of models to use and layer to get different recommendations for a user. We stuck with one that produce 'good enough' results for the hackaton. We have more that we want to experiment with on real data sets.
I'm a product manager by day and a tinkerer by night. I learned new that I don't know a lot... There's lots of performance gains that I can still make to benefit the user as well as keep service costs down. For example, I can choose a different database or I can refactor some code.
What's next for Smart Stream
There are a lot of enhancements that can be done to Smart Stream to improve it's ability to allow users to stay informed and perform optimally. Some improvements are:
Incorporate on-going activity directly related to the user, such as being mentioned in comments, into the recommendation feed so users can rely less on email notifications or the in-app notification pane
Provide alternate categorized views of activities to allow users to even more quickly find what they need. For example, providing a list only of activates where the user is mentioned so they can take action on items directly related to them.
Improve the user experience so the user doesn't have to wait so long for the gadget to load
Improve the recommendations by accounting for more factors and allowing users more ways to train the system on what they need to see.
Built With
ace
amazon-dynamodb
amazon-web-services
heroku
node.js
pandas
python
react
scikit-learn | Smart Stream | Smart Stream keeps you up-to-date on the activities and information you want to know about, eliminating the need to weed through long activity streams or notification lists. | ['Ervin Ebalo', 'Heather Phagan'] | [] | ['ace', 'amazon-dynamodb', 'amazon-web-services', 'heroku', 'node.js', 'pandas', 'python', 'react', 'scikit-learn'] | 137 |
10,045 | https://devpost.com/software/headings | Inspiration
Long and unnecessary information in Jira tickets.
What it does
It extracts different sections of a given document and then displays the headings list.
How I built it
Jira application using Forge
What I learned
Forge. Development and debugging in JS.
What's next for Headings
Publish a similar application for Confluence. Make it more visually pleasing
Built With
forge
javascript
jira | Headings | Get only the main headings in the description of a Jira ticket. | ['Saumya Suvarna'] | [] | ['forge', 'javascript', 'jira'] | 138 |
10,045 | https://devpost.com/software/crowdsourced-intelligence | Confluence Page with Crowdsourced Intelligence Plugin
Mechanical Turk Task Created by Crowdsourced Intelligence Plugin
Inspiration
Crowdsourced Intelligence was born to enable gathering or crowdsourcing intelligence in a quick and automated way for tasks. As a PM, when I’m managing a feature or a project, sometimes there are tasks that need to be completed by a third party that requires human input in order to move that feature along. However, it’s cumbersome to have to manage work outside of your workflow with other tools. That’s how Crowdsourced Intelligence plugin was born. It essentially allows you to pull in a workflow that involves gathering human intelligence tasks right into your existing workflow.
What it does
The plugin allows you to create a task that gets posted to Amazon's Mechanical Turk -- a human intelligence platform for performing manual tasks -- and feeds back in your requested data (i.e. intelligence). In the plugin, you can set specific parameters such as budget, number of responses and the request itself. Rather than having to go onto another platform, in this case Mechanical Turk, this brings that workflow directly into Confluence to make it easier to have one central place to gather and store information. It also allows for easily transferring that same data to developers later on in Jira since all the required info is in one place.
For the demo, I specifically focused on using this plugin for translations. However, because users have the ability to create their own template, this plugin is extensible and customizable to almost any use case that requires gathering (crowdsourcing) data (intelligence) from a third party platform such as Mechanical Turk.
How I built it
Used forge to build the component on React and deploy it on Confluence. A backend server was the used to sync the tasks and uploads and the jobs.
Challenges I ran into
Learning React and how that plays in with the new Forge framework. Fortunately documentation was a breeze and it was fairly easy to make it work.
What I learned
React components is a very powerful base in which to extend from and it was cool to build something to put this to a practical application.
What's next for Crowdsourced Intelligence
Create more use cases through templates
More parameters for customizing tasks
Have an automatic notification sent when all your required responses have been completed
Make the backend component serverless and just deploy it without server (ie. via Amazon or other platform) | Crowdsourced Intelligence | Easily request and manage 3rd party intelligence requests in one simple workflow | ['Cynthia C.'] | [] | [] | 139 |
10,045 | https://devpost.com/software/equation-macro | Equation Macro config
Equation macro display on page
Inspiration
While writing Confluence wiki many a times I felt a need to add equation to my page.
What it does
It helps you add LaTeX equation to Confluence page that will converted to SVG images on the fly to display it beautifully.
How I built it
Using Atlassian Forge and external LaTeX to SVG convertor
Challenges I ran into
I was initially thinking of using internal node based library to do conversion but was not successful so decided to consume external API
Accomplishments that I'm proud of
This is pretty helpful for me as it solves my day to day problem
What I learned
Forge UI and it's basic
What's next for Equation Macro
Caching results, providing more configuration and trying to do it inside Forge environment without using external endpoints.
Built With
confluece
forge
typescript
Try it out
bitbucket.org | Equation Macro | A Confluence macro using Atlassian Forge to display equation as SVG | ['Deepak Jangid'] | [] | ['confluece', 'forge', 'typescript'] | 140 |
10,045 | https://devpost.com/software/sentiment-analysis-em5xvi | What it does
It identifies the positive, negative, neutral polarity in any text, including comments in surveys and social media. It also extracts sentiment at the document or aspect-based level. In order to do this, the local polarity of the different sentences in the text is identified and the relationship between them evaluated, resulting in a global polarity value for the whole text. It returns the sentiment, agreement, confidence and sarcasm of the description in JIRA.
How I built it
This app is available for JIRA. It is built using Forge
What I learned
Forge. Development and debugging in JS.
What's next for Sentiment Analysis
Publish a similar application for Confluence and make it look more visually appealing
Built With
forge
javascript
jira | Sentiment Analysis | Having a Dr. Sheldon Cooper moment? The Sentiment Analysis app will tell you the general sentiment of the description. It also detects sarcasm so "heh heh". | ['Saumya Suvarna'] | [] | ['forge', 'javascript', 'jira'] | 141 |
10,045 | https://devpost.com/software/sifta | Speed up web projects with fast feedback
Simplest way to see how Jira tasks relate to the website
Easiest way to create new Jira tasks that everyone understands
Inspiration
Agile project teams that use Jira, are typically well run and efficient. Projects often breakdown (slow, inefficient, stressful) at stakeholder engagement - feedback, input, approvals.
There's a bunch of tactics, but no real system to make it fast and easy to engage stakeholders in projects. For a number of practical reasons, getting stakeholders to login and learn Jira is usually not possible.
What it does
Sifta is the easiest way for stakeholders to give feedback and agree changes. And the simplest way for everyone to see and share progress.
How we built it
Build with node and mongo, hosted on AWS; using Jira Connect APIs.
Challenges we ran into
Most of the challenges were front end related. Injecting a sidebar list of tasks on to host website that interacts with Jira created many js and css clashes. Particularly finding a reliable way to store element selectors, as well as allowing users to select elements, without triggering event listeners already registered by the host website.
Accomplishments that we're proud of
Much like Jira, we are not just building a tool that does a job. Instead we are building a tool that can be used to support a much more efficient process. Tech teams have long complained about stakeholders not engaging - let's provide some tools that makes it easy for them!
What we learned
You will always run out of time or money before you build all the features you want to build.
What's next for Sifta
We're currently in public beta - excited get as many teams as possible using the product.
Built With
amazon-web-services
mongodb
node.js
rest
Try it out
getsifta.com | Sifta | Stakeholder engagement is often a huge time killer on web projects. Sifta gets fast feedback, thats easy to understand and share, directly in to Jira. | ['Ben Munk - ingen', 'Phil Power'] | [] | ['amazon-web-services', 'mongodb', 'node.js', 'rest'] | 142 |
10,045 | https://devpost.com/software/summarization-e0x1kp | Inspiration
Sometimes JIRA tickets are long and have unneeded jargon. This becomes tiresome to read especially when you are moving between multiple tickets constantly and have to constantly search for the relevance in the long ticket
What it does
The Summarization App, gives a summary for a given document, selecting the most relevant sentences in it to try to sum up what it is about.
How I built it
This app is available for JIRA. It is built using forge.
What I learned
Forge.
Development and debugging in JS.
What's next for Summarization
Publish a similar application for Confluence
Built With
atlassian
forge
javascript
jira | Summarization | Get a two second glance of the contents of a JIRA ticket and never be clueless in a meeting again!!! | ['Saumya Suvarna'] | [] | ['atlassian', 'forge', 'javascript', 'jira'] | 143 |
10,045 | https://devpost.com/software/devpost-forge | Inspiration
As more employees work remotely, it becomes more common that people work in different locations. It helps to see where they were working from to deal with different timezones. This shows you a map of users based on their location when they write a comment.
What it does
It displays a Google Map based on the activity of users that comment on a Jira issue.
How it's built
It uses the Google Maps API and fetches comments submitted by users.
Demo Link
https://devpost-forge.atlassian.net/
Built With
google-maps
react
Try it out
devpost-forge.atlassian.net | Devpost Forge | Displays location based on user activity | ['Emily Lam'] | [] | ['google-maps', 'react'] | 144 |
10,045 | https://devpost.com/software/shortlinks-for-confluence-jira | Shortlink inline dialog in Confluence
Click to copy
Shortlink in Jira issue
Opened shortlink in Jira issue
Try it now!
Confluence:
https://marketplace.atlassian.com/apps/1223134/shortlinks-for-confluence
Jira:
https://marketplace.atlassian.com/apps/1223135/shortlinks-for-jira
Inspiration
Most people are aware of URL shorteners like Bitly for shortening large unwieldy links to make them easier to share. While Atlassian's share feature provides a shorter link, it's still reaaally long.
Atlassian raw link [~96 characters]
yourcompany.atlassian.net/wiki/spaces/SPACE/pages/123456789/Great+for+SEO+But+This+Thing+Is+Long
Atlassian share link [~38 characters]
yourcompany.atlassian.net/l/c/abcdefgh
What it does
Creates short links for Confluence pages and Jira issues.
Shortlink [max 15 characters]
team.sc/abcdefg
Features:
Links automatically created with fast and easy access.
Short and readable domain name: team.sc (think "team shortcut").
Bad words removed from auto-generated link ID.
Super fast 301 redirects using serverless computing at the edge.
How I built it
React and Atlaskit
Cloudflare Worker + Workers KV
Confluence content properties
Jira entity properties
Challenges I ran into
DNS is always a tricky one.
Implementing wildcard routing.
Accomplishments that I'm proud of
Finding a short and readable domain name that was available (albeit expensive).
Determining the best number of characters to go with for the ID. I'm using [a-zA-Z0-9] with no dashes or underscores. With 6 characters you have 62^6 (~56 billion) unique addresses. But with 7 characters you have 62^7 (~3.5 trillion) unique addresses. Since the shortener is limiting URLs to the "*.atlassian.net" hostname it's unlikely to ever hit 56 billion, but adding one more character dramatically increases the scalability. I assume this is why Bitly also uses 7 characters.
What I learned
This was my first Jira app so lots of learnings there. For starters I assumed there would be an equivalent getContentProperty() and setContentProperty() function for Jira. Turns out it's all through REST calls.
What's next for Shortlinks+ for Confluence & Jira
Deploy to the Atlassian marketplace.
Add simple analytics to show visits over time through the short link.
Built With
atlaskit
cloudflare
react
Try it out
marketplace.atlassian.com | Shortlinks+ for Confluence & Jira | Automatic link shortener for Confluence pages and Jira issues. | ['Nathan Waters'] | [] | ['atlaskit', 'cloudflare', 'react'] | 145 |
10,045 | https://devpost.com/software/birdview-for-confluence-cloud | App icon
Inspiration
Our inspirations came from the following observation:
Hard to gain context on our Confluence structure as not all spaces are shown, making finding information difficult
Default way of creating new contents doesn’t provide structural overview making structure planning hard
Navigating around Confluence is hard and slow
Hard to tell what a piece of content contains from the search result as Confluence content doesn’t have page description
The displayed results only display truncated content that might conceal the relevant info that a user is trying to search
What it does
Using the concept of mindmap, this add-on does the following:
Provides an overview of the whole Confluence structure
Provides a description of a content via the page description feature
Organizes content easily via drag and drop feature
Supports
create
and
delete
actions for Confluence content
Supports navigation to a targeted Confluence link
Each node on the mindmap contains a link to the page that can be clicked
How we built it
All interactions with Confluence contents are done using Confluence Cloud REST APIs
For data persistence, all are done using Confluence content properties API
For tech stacks, we use the following:
Serverless
jsmind
library
TypeScript
AUI
Challenges we ran into
Current Confluence Cloud REST API doesn’t support moving pages between different spaces.
Due to this, the drag and drop feature only works for moving Confluence content within the same space.
This is a known issue and there’s already a ticket reported to Atlassian.
Screenshot feature is not yet perfect and can be addressed as an improvement.
Accomplishments that we're proud of
Overall, we are proud of this add-on as it helps with productivity as such it:
Reimagines the way users use Confluence for content manageme
Features such as
create
and
delete
actions and drag and drop features would increase productivity when it comes to content organization
Makes information more transparent hence activites, such as planning, researching and decision-making will be faster.
What we learned
What can and cannot be achieved via the current Confluence Cloud API.
Persistence using content and app properties.
Unsupported content movement across spaces.
What's next for Birdview for Confluence Cloud
Performance optimization
This will arise as the total of Confluence content increases.
Roughly, this can be solved through filtered query, parallelization, etc.
Mindmap personalization at user-level instead of just at system-wide level
Support more actions via the toolbar.
Currently, the toolbar supports a few actions such as taking screenshot, zoom in/out, expand and collapse all.
More features can be added to the toolbar.
Improvements on UX and UI.
Links
This add-on can be installed in Confluence Cloud using this URL:
https://aqsp52asdg.execute-api.us-west-2.amazonaws.com/staging/
Video demo can be found
here
Built With
atlaskit
aws-lambda
jsmind
serverless
Try it out
aqsp52asdg.execute-api.us-west-2.amazonaws.com | Birdview for Confluence Cloud | Your Confluence contents from a bird's eye view, allowing you to visualize your Confluence structure and simplifying Confluence content management and planning. | ['Afif Najib Sohaili', 'Nurul Zaman', 'Hazem Gharib'] | [] | ['atlaskit', 'aws-lambda', 'jsmind', 'serverless'] | 146 |
10,045 | https://devpost.com/software/comala-checklists-for-confluence-forge | Comala Checklists keeps your team focused on what needs to be done. The app's checklists take seconds to create, inside Confluence pages.
Teams might use the app to enable checklist of items related to a page, start an onboarding page, or assign team members project to-do's.
Comala Checklists has the potential to fill a variety of needs. So team members project to-do's can check-off themselves when complete.
With Checklists your team can provide context when completing an item, by leaving a comment on the task to provide additional details.
If you click on Audit log you can view all the information on the actions taken, your team can have transparency in the items pending.
Inspiration
As we were going through the process of attaining SOC 2 certification, it became clear that a lightweight checklists app would be really useful for keeping team members connected to a project. Codegeist gave us the perfect inspiration to utilize Forge to build something we think other teams will really find useful.
What it does
Quickly add checklists of tasks and to-dos to your Confluence Cloud pages. Assign team members to complete these to-dos, and keep track of which have been completed.
How we built it
Our team dove into the process of exploring and learning Forge. We found that it let us prototype and create proof-of-concepts really quickly. In a short amount of time we went from software requirements to an alpha build our team could test internally.
We wanted to explore the full potential of the ModalDialog and how we can store content on a Confluence page, we decided that a core component of the checklist is that is can be auditable by the organization or stakeholders. So we used the Forge Store API we manage to create a backlog of all the checks and un-checks during the lifecycle of the enabled Checklists Macro in a page so we could provide a visual audit trail.
Challenges we ran into
This was our first Forge app, so it was important to familiarize how the Store API and the content-property modules worked together, we ran into an initial problem that our app was not rendering but the Atlassian team was quick to point out the platforms limitations in their documentation and we managed to remove this blocker quickly :)
Setting up a friendly UI was very straight forward and we wanted to build this app with more functionalities using Web Triggers but the team decided to wait for the next release in Forge to implement it, sometimes you cannot have your cake and eat it too :P
Accomplishments that we're proud of
In the beginning we thought that this app could not deliver a lot of value, but it is important to elaborate on the core differences that a checklist provides in comparison to a list. A lot of organizations need their team members to go through auditable processes like - onboarding, review human resource policy or product/service specifications to comply with local, federal or international regulatory compliance.
This is where a checklist can be a very powerful tool that enables individuals or groups to follow strict procedures in a transparent way with just a few clicks and the app can be embedded into any Confluence space.
What we learned
Forge can be a good testing platform so teams can understand what a Function as a Service can do for teams that want to build apps for Atlassian quickly without having to worry about security, since all of this is handle by the Forge service. We have started to work with Amazon Web Services for a few years now and seeing how Forge is built on top of it can give us a glimpse into how server less technology can push software development innovation in the years to come.
What's next for Comala Checklists for Confluence - Forge
We're very excited to see user feedback from Comala Checklists. If the demand is there, we will certainly consider adding additional functionality in the next upcoming releases in Forge as the platform gets ready for prime time.
Built With
api
confluence
forge
forgeui
node.js | Comala Checklists for Confluence - Forge | Generate a to-do list to stay prioritized and focused. Create simple and minimalist checklist of items and tasks, review user tasks and comments. Perfect for meetings, drafting specs & documentation. | ['Naiara Martín', 'Claudio Cossio'] | [] | ['api', 'confluence', 'forge', 'forgeui', 'node.js'] | 147 |
10,045 | https://devpost.com/software/title-0chw1q | Inspiration
In a time where many teams are forced to work remotely and cannot meet face to face, we wanted to provide them with additional insights into employees’ skills and work styles to help form better teams. We also wanted to automate the process in order to save time and provide deeper insights.
What it does
SmartRadarlytics intelligently collects and aggregates user-related data from Jira and builds comparable user profiles in order to create balanced team compositions and optimize collaboration. Each user is evaluated on 5 skills (communication, supportiveness, expertise, meeting deadlines, and productivity). To evaluate each user on these 5 skills, our app automatically retrieves user-related data from Jira and processes it. Up to 5 users’ profiles can be overlaid in the radar chart for easy comparison, so that a well-rounded team can be built.
How we built it
We used Forge to create a Confluence macro, so that the radar chart can be added to any Confluence page. We retrieved the data used to calculate each user’s skills using the Jira API, and we examined user activity like comments, watches, and more. The radar chart itself was built using scalable vector graphics (SVG).
Challenges we ran into
The initial challenge we ran into was deciding what skills would be best to measure and how to choose the best data from Jira to evaluate a user’s skills. To solve this, we researched what skills are most important for team collaboration and cross referenced it with the type of data we could obtain from the Jira API. Another challenge we encountered was ensuring that we designed the chart so that it illustrated only the user’s working style, rather than ranking them among other users. We resolved this by scaling each user’s profile to fit the chart exactly, so that the chart showed each user’s relative strengths and weaknesses, rather than absolute numbers.
Accomplishments that we're proud of
We are proud to have come up with a uniquely automated solution to a task traditionally tackled manually and help teams optimize collaboration despite working in remote environments.
What we learned
We learned all about the new Forge development platform and how to work with the Jira API.
What's next for SmartRadarlytics
The next step for SmartRadarlytics would be to collect more data from more sources like GitHub and Slack, so that we can better represent users’ working styles. We would also like to use machine learning to provide deeper insights into the collected data.
Built With
confluence
docker
forge
javascript
jira
Try it out
codegeist2020forge.atlassian.net
github.com | SmartRadarlytics | SmartRadarlytics optimizes collaboration by helping teams choose a well-rounded set of people with different strengths. The app automatically collects info from Jira and Confluence to evaluate users. | ['Jingbo Wang', 'Emily Chen'] | [] | ['confluence', 'docker', 'forge', 'javascript', 'jira'] | 148 |
10,045 | https://devpost.com/software/askgit-sql-queries-on-git-repository-history-and-data | Homepage with example queries and installation button
The starting UI of the query page
A sample query
A more "useful" sample query
A more complex sample query with graphical output
Inspiration
In mid-June, I built a command-line tool called
gitqlite
, which enables SQL querying of git data. When I heard about the Codegeist Hackathon and read a bit about what's possible with Atlassian Connect + BitBucket, I thought an integration that would
allow users to run SQL queries on their git history and data from BitBucket
would be really cool!
What it does
AskGit adds a section called
SQL Query
to your repository. This includes a SQL editor that permits you to execute arbitrary SQL queries against the commit history and code in your repository. It works with both private and public BitBucket repos, authentication is handled in the background.
The use cases are very broad since this project allows arbitrary querying:
Who checked in code this week? This month? This year?
How many lines are they adding/removing? In what files? In what
types
of files?
Which files have seen the most activity/commit churn?
What's the average time between commits on master?
Who are the most recently active authors?
etc. etc
If the data is in git, and you have a question about it, I hope to make it query-able!
How I built it
This app has two parts:
A query API backend (that uses
gitqlite
) to expose a way to execute SQL queries over HTTP
A (React + AtlasKit) front-end app that serves the UI, handles authentication with BitBucket, makes calls to the query API, and displays results.
The query API is a go service, the UI is a Next.js app, that exposes a description JSON document, the UI that appears in BitBucket, and a homepage to allow users to install the app via a button.
Challenges I ran into
Handling authentication was difficult - needing to learn Atlassian Connect auth flows - validating and producing JWTs, which eventually become access tokens for cloning repositories was one of the main challenges. The documentation was a great help, and so was reading questions/answers from other Atlassian developers, so I'm grateful I was able to figure things out with publicly available resources/documentation and get things working well!
Accomplishments that I'm proud of
I'm really proud of how this app came out generally - in particular the user experience from installation -> first query I find really cool. I'm super impressed by how easy Atlassian has made it for developers to embed additional functionality in their products. A user can begin executing SQL queries against their git data really quick, with authentication handled in the background (works on private repos as well).
What I learned
I learned a lot about what's possible in Atlassian Connect and AtlasKit, as well as what's involved in building an MVP style app integrated with Atlassian products. Doing so has definitely inspired more ideas for potential apps, as well as further improvements to this one!
What's next for AskGit - SQL Queries on Git Repository History and Data
I would love to continue the development of this project. Some very immediate next steps include:
A syntax highlighting SQL editor
Ability to save queries for re-use
More example queries to showcase what's possible
Ability to download/export results in various formats (csv, json, etc)
Improvements to the open-source
gitqlite
project will also improve AskGit. In particular, better query performance, more tables, more SQL functions (for working with git data) will all make the experience of using AskGit + BitBucket awesome.
I'd love to invest in turning this project into a
product
that serves developers on BitBucket (and other platforms)!
I developed this app as an individual (just me!), but am submitting it as an organization - Augmentable Software, a company I founded earlier this year to house and build developer tools like this one!
Built With
atlaskit
bitbucket
go
javascript
react
Try it out
bitbucket.askgit.com | AskGit - SQL Queries on Git Repository History and Data | AskGit is a service that allows developers to run SQL queries on the history and data stored in BitBucket git repos. It creates a new section in the BitBucket repo page with a query editor and runner. | ['Patrick DeVivo'] | [] | ['atlaskit', 'bitbucket', 'go', 'javascript', 'react'] | 149 |
10,045 | https://devpost.com/software/app-store-currency-lookup-widget | Currency Widget -- currency prices for your mobile app skus right in Jira!
Select the currencies to convert to, then the amount
Shows up in the results for developers to use
Inspiration
As a small indie mobile game developer, we need to constantly add new skus for one time weekly sales in our app. Thus, we consistently look up the price conversion for our skus when we are adding new in game products and items. App Store Currency Lookup Widget alleviates this problem by fetching the supported currencies for your mobile app.
What it does
It's a Jira plugin that adds a button to the issues and it will convert your app's base currency to the currencies that you support. It saves the configuration in the Jira settings and looks it up every time you convert a currency, so you don't have to constantly look up the same currency pairings.
How I built it
It's built as a Forge app and it's using an API to call to fetch the latest exchange rates.
Challenges I ran into
The documentation was great in terms of how to set up a Forge app. I'm trying to delete some sample apps I installed via Forge but can't seem to be able to, but that's a minor issue.
Accomplishments that I'm proud of
It's nice to be able to add functionality to Jira, a system that we are already using. I had some issues with the permissions but the lint checker was AMAZING! Good job on that piece Atlassian team!!
What I learned
I think building on Forge is definitely easier than connect if you already know React. It's really a breeze to implement and it's great to not have to set up your own deployment
What's next for App Store Currency Lookup Widget
I look to deploy it to production to help other fellow indie game developers!
Built With
atlassian
currency-rates
forge
react
typescript | App Store Currency Lookup Widget | As an indie mobile game developer, we need to constantly add new skus for sales in app. Thus, we consistently look up the price conversion for our skus. Currency Lookup Widget alleviates this problem. | [] | [] | ['atlassian', 'currency-rates', 'forge', 'react', 'typescript'] | 150 |
10,045 | https://devpost.com/software/mockup-design-integration | Upload progress on an XD file
Editing a description for a Mockup.
An overview of an attachment. In this example, a Figma URL
Changing the default owner on an attachment.
Inspiration
The designer and developer handoff can be overwhelming. You have email exchanges, various project management tools, and a lot can be lost. This plugin was made for designers to link and / or upload hi fidelity mockups, flows, and designs directly to Jira issue tickets. Developers can access files and retrieve their needed assets, flows, and CSS.
What it does
Whether you have a link or a file, this plugin should support them all, without having to install a plugin for each design tool. This tool is made to be an all-in-one design link/upload tool for Jira.
How we built it
This plugin was made with ReactJS and Atlassian Connect together for a fast, lightweight, and a fully Jira integrated app.
Our first step was to connect URLs from design services and save them into Jira storage entity either by retrieving useful data through API or simply linking with some information. The next step was to be able to edit and remove the attachments, and once the CRUD functionality was complete, extra features were needed to make the app more useful such as an upload feature and linking a user/owner to the attachment.
Challenges we ran into
API keys aren’t easy to come by, so we had to make do with our limited resources to support the many design services in any way we can.
Accomplishments that we're proud of
The plugin is a fully robust app that supports notification, upload, API communication, and storage to retain useful data.
What we learned
We learned how easy it was to create a plugin for Jira to make our work environment more comfortable. The ability to create a plugin with ReactJS gave us the ability to hit the ground running. Also, the documentation to create a Connect plugin was very thorough and easy to follow making the plugin development a breeze.
What's next for Mockup Design Integration
There are many features we wish we could implement if we had more time such as an assets portion to include more files, urls, or other for each attachment.
We are also still waiting for API keys to fully integrate the design services better with our plugin.
Built With
atlassian
react
Try it out
jira-design.herokuapp.com
github.com | Mockup Design Integration | This plugin was made for designers to link and / or upload hi fidelity mockups, flows, and designs directly to Jira issue tickets. | ['Jenearly Ang', 'Yenith LianTyHao'] | [] | ['atlassian', 'react'] | 151 |
10,045 | https://devpost.com/software/follow-up-6crsmi | Inspiration
Our project report consists of problems found and the proposed solutions. A follow up of the solution in JIRA would be a helpful feature.
What it does
Follow up issues on Jira
How I built it
Challenges I ran into
Accomplishments that I'm proud of
What I learned
What's next for Follow Up
Built With
bitbucket
jira
Try it out
bitbucket.org | Follow Up | Follow up issues on Jira | ['Tri Labs'] | [] | ['bitbucket', 'jira'] | 152 |
10,045 | https://devpost.com/software/text-classification-for-jira | What it does
Text Classification assigns one or more classes to a document according to their content. Classes are selected from a previously established taxonomy (a hierarchy of categories or classes). This app takes care of all preprocessing tasks (extracting text, tokenization, stopword removal, and lemmatization) required for automatic classification.
This app supports a variety of text classification scenarios like:
Binary classification like spam filtering (HAM, SPAM) or simple sentiment analysis (POSITIVE, NEGATIVE).
Multiple class classification like selecting one category among several alternatives - movie genre classification (thriller, terror, romantic, etc.)
Multilabel categorization - assigning all categories that apply to a single document
Complex taxonomy categorization - assigning categories arranged in a multilevel taxonomy
The app combines statistical document classification with rule-based filtering, which allows us to obtain a high degree of precision in a wide range of environments.
Try it out with some sample text!
How I built it
Using Forge UI and API
Challenges I ran into
Getting started with Forge
Accomplishments that I'm proud of
A working app
What I learned
Forge
Atlassian developer products
What's next for Text classification for JIRA
Better visualization of app response output.
Same feature for Confluence.
Built With
forge
javascript
Try it out
github.com | Text classification for JIRA | This app performs text classification for JIRA issues. Text Classification classifies texts based on a hierarchical categorization or taxonomy. It can be used for several NLP based applications. | ['Mashrin Srivastava'] | [] | ['forge', 'javascript'] | 153 |
10,045 | https://devpost.com/software/linguistics-information-for-jira | What it does
Forge app for JIRA ticket descriptions' linguistic information. This can be used as a base for any NLP related tasks that other developers would like to build for JIRA analytics.
This app will provide- Lemmatization, PoS, and Parsing for various linguistic analysis in several languages: morphosyntactic analysis, PoS (Part of Speech) tagging, and lemmatization.
Even though it is simple in name, it contains a myriad of functionalities derived from the complete morphosyntactic and semantic analysis it carries out. Through this app, one will be able to carry out some of the most used tasks in linguistic applications, all of the different aspects of the morphosyntactic and semantic analysis:
Syntactic analysis: obtains a thorough syntactic analysis, giving a complete syntactic tree where the leaves represent the most basic elements and their morphological and semantic analyses.
Lemmatization: obtains the lemmas of the different words in a text.
PoS tagging: obtains not only the grammatical category of a word but also all the possible grammatical categories in which a word of each specific PoS type can be classified (check the tagset associated). In the cases it applies, the morphological analysis will be related to semantic analysis.
How I built it
Using Forge-UI and Forge-APIs.
Challenges I ran into
Getting started with Forge.
Accomplishments that I'm proud of
A working app.
What I learned
Forge.
About Atlassian developer products.
What's next for Linguistics information for JIRA
Better visualization of information rather than JSON response.
Similar app for Confluence.
Built With
forge
javascript
jira
Try it out
github.com | Linguistics information for JIRA | Forge app for JIRA ticket descriptions' linguistic information. This can be used as a base for any NLP related tasks that other developers would like to build for JIRA analytics. | ['Mashrin Srivastava'] | [] | ['forge', 'javascript', 'jira'] | 154 |
10,045 | https://devpost.com/software/kpi | Inspiration
Our current project requires a daily, weekly, and monthly report which involves a KPI indicator. We would like to improve the reporting experience by enabling an insightful KPI indicator.
What it does
Key Performance Indicator visualization.
How I built it
Challenges I ran into
Accomplishments that I'm proud of
What I learned
What's next for KPI
Built With
jira
tableau | KPI Viz | Interactive Key Performance Indicator (KPI) Visualization | ['Tri Labs'] | [] | ['jira', 'tableau'] | 155 |
10,045 | https://devpost.com/software/jira-language-identification | Identifies language as English
Inspiration
Often in open source projects, the developers are from various demographies and hence might be comfortable in their native language. Several times in various communities, bug trackers, etc., users post in their native language and it is often difficult to even figure out the language being used by the developers. This will solve this problem and will also help to further use this information to extend to more functionalities like translation, etc.
What it does
Language Identification app automatically detects the language of texts in the JIRA ticket.
Identifies the language of any text, from a list of more than 160 languages. It's based on the franc library, which bases the language detection process on N-grams. It supports different scripts and provides the language results using the ISO639 standard (both for two and three characters).
Example for English:
https://www.youtube.com/watch?v=RHyogCg-V_U
Example for Spanish:
https://www.youtube.com/watch?v=7-cy5gz4KhA
How I built it
Using Forge-UI and API
Challenges I ran into
Getting started with Forge.
What I learned
Forge.
What's next for JIRA Language Identification
Integration with more apps that can build on top of it.
Same feature for Confluence.
Built With
forge
javascript
Try it out
github.com | JIRA Language Identification | Automatically detects the language of texts obtained for a JIRA issue description. It can be used as a base app for other apps like translation, etc. | ['Mashrin Srivastava'] | [] | ['forge', 'javascript'] | 156 |
10,045 | https://devpost.com/software/create-page-from-content-for-confluence | Create new page from highlighted fragment
Inspiration
The idea for the application came from our technical writer, who often creates skeleton documentation for the end-user based on the analyst's requirements, which are gathered in Confluence. It is always tedious to work on a copy-paste basis. Switching between pages is very annoying when you have to create more than 20 pages (depending on the complexity of the product). We wanted to speed up the process of creating new pages that will be filled with content already contained on existing confluence pages.
What it does
This app allows you to create a new Confluence page based on the highlighted text on the page (after clicking Create a new page in the context menu). A new page is created as a child of the current page.
Instead of
seven
clicks (1. copy the text, 2. click Create new page, 3. select page type, 4. click Create button, 5. enter the title, 6. paste the copied text, 7. publish page), a user should make
four
quick actions: highlight text, click Create a page in the context menu, enter the title and click Save. Apart from saving time, he doesn't lose the context of the site he is currently working on.
How we built it
We used Forge UI components which helped us create the front end of our app:
ContextMenu
Form
Text
InlineDialog
We also used Forge Confluence fetch API which is a partial implementation of node-fetch and includes an Authorization header based on the context-bound fetch call.
We manage the entire project using Jira Cloud and Confluence. We have prepared the interface graphic designs in Figma.
Challenges we ran into
The problem was that through the contextual object
selectedText
we can only pass clean text without formatting. Unfortunately, the entire page structure and formatting cannot be moved to the new page. So we can't copy all page elements when creating a new page. This is a big limitation for this application, because, on the one hand, the user gains time, having functionality at hand, on the other hand, the time saved must be spent on reformatting the text.
This limitation we reported to the Atlassian team.
Accomplishments that we're proud of
Our beginnings with Forge were very difficult. That is why we consider it successful that the application works. What's more: it works correctly.
The strength of our solution is the
lack of configuration
. The application is installed and is immediately ready for use. Functionality is at hand, easily accessible.
We think that the design of the panel (glance) and the mechanics of the application's operation do not differ from the Jira standards. We believe that it is important that the end-user does not feel that he is using an external application. Our application fits perfectly into the product offered by Atlassian. Creating a new page is as easy as adding a comment - Confluence users know this action.
What we learned
This was our first contact with Forge, so everything was new to us. We learned how Forge works, what is currently possible to achieve, what not yet. In case of this app, it was important to learn how to work with Confluence fetch API and
/wiki/rest/api/content
resource. Worth noticing that having React background was really helpful to create the app quickly.
None of us has ever participated in any hackathon!
We work with each other every day, but it is a completely different style of work than during such a competition. We were still thinking about how little time we have left, and how much is still to be done. But we can say it was worth it and it certainly is not our last time. We still want to work together :)
What's next for Create Page from Content for Confluence
The most important functionalities we would like to add to the application are:
defining the location of a new page in the tree
save the selected fragment as a template
A lot depends on how much Forge will offer us and in what direction its possibilities will develop. Currently, Forge is not supported on the Atlassian Marketplace. (We are looking forward to adding such support!) For this reason, we decided to
add this functionality as a new feature in the existing Connect app -
Content Template Macro for Confluence
and publish it on the Marketplace.
Built With
forge | Create Page from Content for Confluence | Create a new Confluence page with just one click. This page is not empty - all using existing content! Highlight the fragment, add a title and enjoy the newly created page. | ['Krzysztof Skoropada'] | [] | ['forge'] | 157 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.