Software change management solution

[ToniSalmonelli]

Hi there,

I am looking for a web based, GPL solution to manage software changes.

Scenario would be more less like this:

3 groups: business, functional consultants, devs.

1. Business posts request for a new or a change of existing functionality - a ticket with attachment.
2. Functional consultant kicks in. Works on details, starts exchanging messages with business group and posting detailed information for the dev group.
3. Ticket is passed to the dev group, status is set to /In development/.
Devs can communicate with functional consultants in the same way as in point 2.
Optionally functional consultants can pass devs messages to the business group.

4. Devs finish their work, set the ticket's status to /Internal testing/, pass the ticket to the functional consultants group.
5. Functional consultants check the solution, either change the status back to /In development/ (and pass it to the dev group) or to /Testing/ (and pass it to the business group).
6. Business group does it's work, changes status to /Internal testing/ or /Production/.

Notifications about a change of status or a posted message should be sent via e-mail.
Would be nice to be able to define all three groups per ticket.

The closest one I've found is Mantis Bug Tracker, but maybe you guys know other solution(s) worth checking.

Thanks.

 

[purbeast0]

Look at the Atlassian tool suite. I'm a fan of Jira and you can do everything you need with Jira and the way boards with within it.

 

[mxnerd]

https://alternativeto.net/software/mantis-bug-tracker/

Redmine seems very interesting.

 

[ToniSalmonelli]

Jira is not free, maybe not much of a cost, but passing this through finances might be a long process.
Tried OpenProject as an alternative, but it is not quite what i'm looking for.

Will have a look @ Redmine.

 

[purbeast0]

Well you never said cost was an issue.

Just remember, with software, a lot of the time "you get what you pay for" is very true.

 

[ringtail]

Hi there,

I am looking for a web based, GPL solution to manage software changes.

Scenario would be more less like this:

3 groups: business, functional consultants, devs.

1. Business posts request for a new or a change of existing functionality - a ticket with attachment.
2. Functional consultant kicks in. Works on details, starts exchanging messages with business group and posting detailed information for the dev group.
3. Ticket is passed to the dev group, status is set to /In development/.
Devs can communicate with functional consultants in the same way as in point 2.
Optionally functional consultants can pass devs messages to the business group.

4. Devs finish their work, set the ticket's status to /Internal testing/, pass the ticket to the functional consultants group.
5. Functional consultants check the solution, either change the status back to /In development/ (and pass it to the dev group) or to /Testing/ (and pass it to the business group).
6. Business group does it's work, changes status to /Internal testing/ or /Production/.

Notifications about a change of status or a posted message should be sent via e-mail.
Would be nice to be able to define all three groups per ticket.

The closest one I've found is Mantis Bug Tracker, but maybe you guys know other solution(s) worth checking.

Thanks.

GitHub

 

[ultimatebob]

Jira is basically the standard for software project management now. That's not to say that Mantis is bad, as I've used it before in a past job. It's just not the right tool for the job if you also need a place to collect project specifications as well. That's what a tool like Confluence is for.

Just get the Atlassian Cloud product, which includes both Jira and Confluence. It's a hosted solution that you do not need to maintain, and it's pretty cheap (Like under $100 a month) if you only have a small handful of users.

 

[beginner99]

Just get the Atlassian Cloud product, which includes both Jira and Confluence. It's a hosted solution that you do not need to maintain, and it's pretty cheap (Like under $100 a month) if you only have a small handful of users.

Finance wise probably the best way to go or just use GitHub issue tracking. Rolling out your own internal system for handful of people is just way more costly (and risky) in the long run.