Is Jira a good tool for managing a customer implementation project of software and hardware?

[Kyle Freitas]

The implementation is mostly, testing software features before moving to production, creating documentation, providing customer training, moving code to production, updating final documentation and final regressive testing.

Does Jira provide the visibility across my internal cross functional teams and with the external customer with:

- major milestones and supporting tasks

- time lines (estimated and actual)

- asset allocation (staff and available work hours)

- project task interdependencies and sequencing

- reports for tracking current and projected task completions, milestone executions and estimated vs. actual project status.

[Amy Harvey]

Looks like no one ever responded to this question; but I have the same one.  Kyle- did you end up finding a solution to this, or using JIRA to manage your client-facing implementations?

[Everett Cavazos]

@Kyle Freitas and @Amy Harvey I just finished architecting/building an entire Implementation Project Plan environment in Jira for the customer success team at my company. They are currently using TaskRay but are looking to move to Jira. It includes the ability to allow a customer to interact with their To-do items and to set them to resolved.

It included an entire customization: new issue types, multiple customized workflows with conditions, project permission scheme updating, and issue security policy and scheme. I tested it with a test user and it does work.

As far as your ultimate question of it being a "good tool." That remains to be seen and subjective. It will require a little bit of hand-holding/education to the customer but it is fairly straightforward. I personally think it works great!

[Everett Cavazos]

Oh wow sorry I just realized how old this thread is, apologies!