Seeking Jira Survivors

#1

Post by troy55_yort55 » Thu, Jun 19, 2025, 8:44 PM UTC

Re: Seeking Jira Survivors

#2

Post by troy55_yort55 » Thu, Jun 19, 2025, 8:44 PM UTC

We are actively building a new approach to jira, putting dev's in control of more of the lifecycle and better support for x-functional teams.

We are in need of critical feedback as we're starting to build what we love and need more opinions.

If you are willing to help out we will happily set you up in our swag (capybaras) and give you a license for your future use.

1) sign up for free at www.atono.io 2) join slack and provide feedback or hit me directly troy.mcalpin@atono.io

Re: Seeking Jira Survivors

#3

Post by baobun » Thu, Jun 19, 2025, 10:33 PM UTC

troy55_yort55 wrote: post #2

We are actively building a new approach to jira, putting dev's in control of more of the lifecycle and better support for x-functional teams. We are in need of critical feedback as we're starting to build what we love and need more opinions. If you are willing to help out we will happily set you up in our swag (capybaras) and give you a license for your future use. 1) sign up for free at www.atono.io 2) join slack an…

Website doesn't load anything without JS.

While I understand using the tool itself might require client-side JS for features, an accessible web site would inspire confidence that you care about efficiency and accessibility and that the tool won't become the bloated hog Jira is.

Re: Seeking Jira Survivors

#4

Post by troy55_yort55 » Fri, Jun 20, 2025, 2:23 AM UTC

baobun wrote: post #3

troy55_yort55 wrote: post #2

We are actively building a new approach to jira, putting dev's in control of more of the lifecycle and better support for x-functional teams. We are in need of critical feedback as we're starting to build what we love and need more opinions. If you are willing to help out we will happily set you up in our swag (capybaras) and give you a license for your future use. 1) sign up for free at www.atono.io 2) join slack an…

Website doesn't load anything without JS. While I understand using the tool itself might require client-side JS for features, an accessible web site would inspire confidence that you care about efficiency and accessibility and that the tool won't become the bloated hog Jira is.

Good point! We’ll look into a ‘progress enhancement’ strategy to adjust our content delivery based on browser configuration. Any interest in having a look at the app?