Project management, bug tracking, and support

K

_kabal_

Executive Member
Joined
Oct 24, 2005
Messages
8,290
Reaction score
4,564
Just wondering what software or combinations of software teams out there are using to manage the full lifecycle of product development.

Currently we are using Trello for sprints, mantis for bug tracking, and Cerberus for support. All of these tools work well in isolation, but it can be quite confusing for clients.

I am looking for a more holistic solution.

What are teams out there using successfully?
 
I've used Zapier in the past to help with integration between some apps so that duplication is less. My company also liked each tool on its own but for someone that needs to work in all of them it was a nightmare (used different tools). We used Wrike for task tracking for customers, so i setup zapier to create trello tasks automatically from Wrike.

Dont know if your tools are supported, but have a look:
https://zapier.com/
 
We are busy fully migrating to TFS (Visual Studio Team Services). One of the better options available out there...

(we are using git in TFS for source control)
 
are you guys using service desk + jira?

how are you letting clients log bugs/support tickets?
 
Jira + Confluence.

Support tickets logged via email, easiest method for the end users ( although they still don't use it! )
 
It's old but Redmine is still quite feature packed.
 
Jira and confluence. As a pm, I didn't like it at first, but then I discovered plugins.

/kicks ma project to the curb
 
Kosmik said:
Jira + Confluence.

Support tickets logged via email, easiest method for the end users ( although they still don't use it! )
Click to expand...

Do you mean that clients send emails that then automatically become bugs in jira, and they get notified of status updates?
 
Kosmik said:
Pretty self explanatory, work through the admin or guide.



yes. You set up handlers per project and can do autoassigns to team members or teams.
Click to expand...

Ah I see. That could get quite expensive if you have it setup to create users. But without it creating users, they cannot get status updates.
 
_kabal_ said:
Ah I see. That could get quite expensive if you have it setup to create users. But without it creating users, they cannot get status updates.
Click to expand...

No. You setup Jira users i.e.: developers etc. They have full access to the system and can update items, resolve etc. Everyone else is not a user on the Jira system but they can still log tickets via the mail handling. Jira will update the mail instigator, recipient and any viewers that a Jira user adds to a ticket.

For example, a dev team consists of 8 members. There are multiple projects as well as cross projects ie: project covering many projects - Reporting etc. There are project champions in the dev team who receive the principal notification and then re-assign amongst the team as needed. People submit bugs, dev requests, stories etc via email to the mail handlers created for the above projects. Because they submitted it, Jira tracks the sender and will feedback to them regarding any changes on the tickets that they created.

*edit* just a note on our current running setup, we linked our AD but only devs are allocated to the "Jira Users" role. This is where your licensing comes off. The others are linked and Jira can see them but they are not able to interact with the system save for viewing or email feedback/logging.
 
Last edited:
Kosmik said:
Pretty self explanatory, work through the admin or guide.



yes. You set up handlers per project and can do autoassigns to team members or teams.
Click to expand...

:erm: don't have admin access but will forward Phoenix link onto our guys that maintain it
 
I actually just setup another trail jira cloud instance.

Although I was able to log tickets from my other email address, any status updates or comments that I made as the admin/developer didn't result in email notifications
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X