Comments (4)
The honest answer is "I have no fucking clue".
We stopped actively using Mantis in favor of LaunchPad at version 1.2.5 in November 2011. Hence why there have been no updates to this code.
If Mantis's design is clean, I would expect the API to remain stable throughout the 1.2.x series, but beyond that, I really couldn't tell you.
from gauge-support.
Thanks for the answer. BTW, why did you jump ship ?
from gauge-support.
End users, mostly.
Mantis is very technical. LaunchPad has distilled (read: dumbed down) the whole process of reporting a bug into a few input fields, spread out over multiple pages, while scriptically holding the user's hand.
As a developer, I liked Mantis. It has fields for almost everything and is very flexible. But I spent a lot of time moderating and fixing up end users' tickets, because they couldn't handle the complexity.
I seriously went as far as adding a representation of MS Office's clippy to pop up when what they were entering couldn't possibly make sense, and added code to make the submit button jump around if they were about to submit bullshit.
Put bluntly: Mantis is a very nice tool for technicians, but our end users were no technicians.
Add to that that Mantis (at least back then) had some very interesting/questionable coding decisions and only ever seemed to gain new features when someone was desperate enough to code them (i.e. an itch-based development, rather than planned or product based development), and that its overall look and feel seemed a bit dated, and looking at other options became even easier.
I would still recommend Mantis as your tracker if your hosting is PHP-based and your users (or workflow) are compatible with it.
It's sort of like an ended relationship...it's not that I stopped loving Mantis, it just didn't work out anymore. ;)
from gauge-support.
Wow, that was a very thoughtful and thorough answer which made me laugh. I appreciate the perspective. Especially because I'm used to github and more of the flashier types of BTs. I though that mantis was outdated. a relic still used by people set in their ways and not open to the UI changes of today. Your perspective offers the paradox of Mantis's situation, a sophisticated BT that is not keeping with the times and a tragic development paradigm.
Also, hilariously tragic to think how desperate you were that you needed to invoke MS Clippy. Sorry to hear that man, [shoulder pat]. BTW, I also liked your analogy of an 'ended relationship' as well. Apropos.
Cheers!
Edit: typos
from gauge-support.
Related Issues (2)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gauge-support.