We have received multiple request from customer telling us that they would like to have a feature that would help them in generate a Salesforce.com report that would shows all the associated JIRA issue.
At the moment, the information for the associated JIRA issues can be retrieve via the VisualForce page. But it is not possible to include those information in Salesforce.com Report.
Victor Law
We could definitely use this feature. Our support teams mainly work in Salesforce, and even though they have Jira access it is inconvenient for them to switch between systems to find this.
Attachments Open full size
Looking forward to this feature
Attachments Open full size
Definitely a needed feature.
Attachments Open full size
this is a critical feature, i am now looking into the connector and without this feature, I am not sure we can use this connector. it is critical for us to report our escalated issues (escalated issues to development are represented by jira tickets)
Attachments Open full size
Fully agree with Kyle. My teams have access to Jira also but the main tool for our support is Salesforce and not being able to find which tickets that have a attached Jira (or multiple) is going to be a hassle.
Some of this may be possible to work around by mapping fields but as soon as there is more than one Jira for a support case this becomes even more tricky.
Attachments Open full size
Kyle, thank you for your feedback. It does seem like a pain for the Salesforce people. We are not actively working on this feature at the moment, but more research will be conducted and we might reach out to you at some point soon to help with the requirements.
In the meantime, is it necessary to tie the report to the native Salesforce Report and Dashboard functionality?
Attachments Open full size
This was a disappointing discovery when implementing across our 3 Tier product support process. Support Agents and Management with access to Salesforce but not JIRA (By design for business purposes) don't have a way to run metrics or even simply identify Cases with JIRA Associations. Tier I agents are required to add several steps in their workflow to track and manage these cases. Even a simple boolean indicator would be enough as a V1.0 feature.
Attachments Open full size