Deviniti · 2020–2024 · Atlassian and monday.com apps

Other apps I've designed

At Deviniti I designed for six marketplace apps for Jira, Confluence and monday.com. I took three of them from an idea to launch and helped three established apps grow. Two have full case studies; here is a short overview of all six: my role, what I designed and what came of it.

Actions for Jira Service Management

  • Built from scratch
  • Platform: Jira Service Management (Cloud)
My role
UX/UI Designer
Time on the project
~1 month, part-time, during a hackathon
Marketplace
4.7/5 on the Atlassian Marketplace (October 2026)
Actions for JSM configuration: edit form title, editable fields and request types.
Request editing configuration in Actions for Jira Service Management. Admins set the edit form title, choose which fields can be edited and pick request types.Open full size

What it is: Lets service teams decide which changes customers can make to their own requests on the Customer Portal, so agents spend less time on small edits. Jira admins set the actions up; customers simply use them.

What I did

The need had already been validated, so the work went straight into design. On a hackathon timeline I designed the UX and UI of the MVP within the agreed scope.

What I designed

  • Request actions: customers edit their requests directly on the Customer Portal, within the limits the admin sets.
  • Internal comment settings: every change a customer makes leaves an internal comment that only agents can see. Admins can keep the default text or write their own with variables, up to 400 characters.

Outcome: The app won a Marketplace Award at Atlassian Codegeist, Atlassian's developer hackathon.

Integrator for Confluence & Jira

  • Built from scratch
  • Platform: Jira and Confluence
  • No longer on the marketplace
My role
Product Owner and UX/UI Designer
Time on the project
~1 year
Marketplace
No longer available: Atlassian built the same capability into its products
Generated pages configuration in Jira: a JQL condition that decides for which issues a Confluence page is created.
Generated pages configuration in Jira. A JQL condition decides for which issues a new Confluence page is created and shown on the issue.Open full size

What it is: Brought Confluence into Jira. People could see related Confluence pages on a Jira issue and create Confluence pages from Jira issues automatically, all set up on one configuration page.

What I did

The app existed only as a hackathon prototype that had never been released. As Product Owner and designer I:

  • redesigned its screens,
  • decided which features it was missing for a first release,
  • designed those features and took the app to the Atlassian Marketplace.

Once the app had customers, I chose to focus on design and handed the Product Owner role to a colleague.

Outcome: The app launched on the marketplace and its customer base kept growing. It was developed until Atlassian added the same capability to its own products.

Support Pulse

  • Built from scratch
  • Platform: monday.com
  • No longer on the marketplace
My role
UX/UI Designer and Researcher
Time on the project
~15 months (January 2023 to March 2024)
Marketplace
No longer available: monday.com built a native customer portal
Portal setup inside monday.com: a step-by-step wizard for page, categories, request view and request list.
Portal setup inside monday.com. A step-by-step wizard guides admins through page, categories, request view and request list, with a live preview on the left.Open full size

What it is: A customer service portal for monday.com. Customers send and track their requests in one place, and agents handle them without leaving monday.com.

What I did

  • Ran the discovery: interviews with implementation partners, a site visit, community and competitive research.
  • Turned the findings into three core needs and designed the portal, its setup wizard and the agent view end to end.
  • Cut the scope to an MVP together with the product manager when the launch date moved forward.

Outcome: The app won its first customers in its first week on the monday.com marketplace. We stopped developing it in March 2024, after monday.com announced a native customer portal.

TestFLO – Test Management for Jira

  • Grown and improved
  • Platform: Jira
My role
UX/UI Designer, the first on the team
Time on the project
~2 years
Marketplace
4.3/5 on the Atlassian Marketplace (October 2026)
TestFLO Test Plan Execution Report: test case counts by status, an execution progress bar and a list of test cases with their statuses.
Test Plan Execution Report. Test cases summarised by status, an execution progress bar, and a list of test cases with their requirements and defects.Open full size

What it is: A test management app built into the Jira issue view. Teams with mature, complex testing processes choose it because almost everything in it can be configured.

What I did

I joined when TestFLO was already a large, mature product, as the team's first UX/UI designer. I designed new reports and test plan operations that had to fit an established, highly configurable app.

What I designed

  • Requirement Traceability Report: follows each requirement through test case templates, test cases, their runs in an iteration and the defects they raised.
  • Next iteration: starts a new round of testing from a test plan using one of four strategies. Statuses reset, and the history of earlier runs stays available.
  • Master Test Plan and its execution report: groups several test plans into one larger object and shows their combined progress, filtered by version or by custom filters.
  • Test Plan Execution Report: shows how a test plan is progressing, by test case status or by step progress.

Outcome: While I worked on TestFLO, the app won 3 new enterprise customers.

Queues for Jira & JSM

  • Grown and improved
  • Platform: Jira Service Management
My role
UX/UI Designer
Time on the project
~10 months
Marketplace
4.6/5 on the Atlassian Marketplace (October 2026)
Queue editing screen in Queues for Jira: visibility, issues to show and columns. Notification settings for issues matched by JQL, with an option to highlight selected issues in color.
Editing a queue. Admins set who can see it, which issues and columns it shows, and turn on notifications that highlight new issues.Open full size

What it is: Goes beyond the built-in queues in Jira Service Management. One queue can cover several projects, visibility can be limited to chosen people, and queues can be organised into groups.

What I did

I worked with the product manager and a Scrum team: I analysed user needs, built prototypes, tested them with users and delivered high-fidelity designs.

What I designed

  • Notifications: new issues in a queue are highlighted in a colour the admin chooses, so none get missed. Admins decide, per queue, whether to highlight all new issues or only some.
  • Bulk changes: change who can see many queues, or which columns they show, in one step.
  • Queue groups: groups and subgroups for a multi-level structure, which can be hidden when not needed. Group administrators manage every queue in their group.

Outcome: Each of these features made the app more attractive to customers, until Jira's native queues were no longer a real alternative.

What I'd do differently: I'd replace drag and drop with a simple selector. Drag and drop needs both a keyboard alternative and a single-pointer alternative to meet WCAG 2.2 (2.1.1 Keyboard, 2.5.7 Dragging Movements); a selector meets both from the start.

RTM – Requirements and Test Management for Jira

  • Grown and improved
  • Platform: Jira
My role
Sole UX/UI Designer
Time on the project
~10 months (July 2022 to April 2023)
Marketplace
4.4/5 on the Atlassian Marketplace (October 2026)
RTM import screen: a four-step flow with location, format type, file encoding, delimiter, import options and a file drop zone.
Importing test cases into RTM. A four-step flow (upload file, map fields, confirm, finalize) with the import settings on the first step.Open full size

What it is: Requirements and test management inside Jira, used by teams that need to show how requirements are covered by tests.

What I designed: Document View for sign-offs, import and export, and the app settings.

Outcome: Document View reached 15% feature adoption within a month of release (measured in GA4, without segmentation).

Also at Deviniti

I also redesigned the Deviniti Support Center, where customers find documentation for all of the company's apps. I ran workshops with the support lead, mapped the existing user journey and its pain points, proposed a new layout and used card sorting to organise the content. I finished the high-fidelity design together with a second designer.