Classic Connector for | Ideas for ServiceRocket's Atlassian Apps

1 Vote
- Add my vote +1
- +2
- +3
Increase the number of events and be able to filter by event under the Diagnostic tab

It would be great to: increase the events under the diagnostic tab able to filter by event

Created 14 Feb 05:04pm by Aaron Pavez

Classic Connector for Salesforce and Jira (Server)

0 Needs review
10 Vote
- Add my vote +1
- +2
- +3
As an Admin , i would like to extend the permission to manage the app to normal users (add mapping)

We don't want to promote the project admin as a Jira admin, but on the other side, we would like to let him manage the settings of the mappings.

Created 11 Nov 05:36pm by Aaron Pavez

Classic Connector for Salesforce and Jira (Server)

0 Needs review
30 Vote
- Add my vote +1
- +2
- +3
2 Salesforce connections can escalate to same issue type on one JIRA instance

Hi, We currently encounter one issue. We have 2 Salesforce instance which are for different customer types. Then both the Salesforce instance need to escalate case to same issue type in one JIRA instance. Now seems it is unachievable when we con...

Created 18 Dec 02:55am by Jing Gao

Classic Connector for Salesforce and Jira (Server)

0 Will not implement
4 Vote
- Add my vote +1
- +2
- +3
As a user, I would like to have all mapped fields go back to being clear when unlinking associations

Currently, if an existing association is unlinked, the mapped fields of said past association will still contain the values existing before the unlinking was executed. It would be great to have the option to either clear these fields or for them t...

Created 26 Aug 11:01pm by Carmen Mendez

Classic Connector for Salesforce and Jira (Server)

0 Needs review
7 Vote
- Add my vote +1
- +2
- +3
I want to be able to map Jira issue types to multiple obejct types as in the new Connector

Customer pointed out that they'd like to have the option to be able to map Jira issue types to multiple object types that way they can be created and work with from multiple objects in Salesforce

Created 27 Dec 03:50pm by Amir Alvarez

Classic Connector for Salesforce and Jira (Server)

0 Needs review
33 Vote
- Add my vote +1
- +2
- +3
As an User, I want Salesforce Rich Text field (HTML) is compatible with JIRA Text field (Wiki)

As an User, I want Salesforce Rich Text field (HTML) is compatible with JIRA Text field (Wiki) If I mapped the Salesforce Rich Text field with JIRA Description field, it will display the content as HTML.

Created 6 Mar 06:30am by Kevin Lew

Classic Connector for Salesforce and Jira (Server)

5 Needs review
1 Vote
- Add my vote +1
- +2
- +3
Limit the JQL remoteObjects search for Jira issuess linked to SalesForce cases

It would be great to be able to limit the search based on a specific field. Such that certain SF fields are available for searching only if there is a specific value in the case, e.g., only return results on Account.Name if the case’s IsRestricted...

Created 13 Dec 09:56pm by Aaron Pavez

Classic Connector for Salesforce and Jira (Server)

0 Needs review
14 Vote
- Add my vote +1
- +2
- +3
As a user I need the ability to pull changes only to specific Jira issues

The current behaviour for the "pull changes" action from the "Manage Application Links" menu of a Jira issue associated with a Salesforce object will pull the changes and apply them to any other Jira issue associated with the same Salesforce objec...

Created 11 Dec 01:16pm by Juan Recabarren

Classic Connector for Salesforce and Jira (Server)

0 Needs review
4 Vote
- Add my vote +1
- +2
- +3
As a user, JIRA comments exceeding 4,000 characters should be trimmed accordingly (bellow 4,000)

Due to Case Comment limitation to 4,000 characters, JIRA comments that exceeds 4,000 will not be synched. This feature request is to have the connector to trim comments with over 4,000 characters, so that at least part of the comments are synched.

Created 11 Apr 08:24pm by Immanuel Siagian

Classic Connector for Salesforce and Jira (Server)

1 Needs review
7 Vote
- Add my vote +1
- +2
- +3
Show Full name instead of username when mapping the Jira assignee field

In Jira the assignee field shows the "Fullname" of a user. When you map that field to Servicerocket you will get the username instead. It would be good if that could be Full name as it's presented in Jira. See also SRSUP-6367

Created 15 Aug 03:10pm by Guest

Classic Connector for Salesforce and Jira (Server)

1 Unlikely to implement

Ideas for Atlassian Apps

by ServiceRocket

Filter by status

Filter by category

Increase the number of events and be able to filter by event under the Diagnostic tab

As an Admin , i would like to extend the permission to manage the app to normal users (add mapping)

2 Salesforce connections can escalate to same issue type on one JIRA instance

As a user, I would like to have all mapped fields go back to being clear when unlinking associations

I want to be able to map Jira issue types to multiple obejct types as in the new Connector

As an User, I want Salesforce Rich Text field (HTML) is compatible with JIRA Text field (Wiki)

Limit the JQL remoteObjects search for Jira issuess linked to SalesForce cases

As a user I need the ability to pull changes only to specific Jira issues

As a user, JIRA comments exceeding 4,000 characters should be trimmed accordingly (bellow 4,000)

Show Full name instead of username when mapping the Jira assignee field

Filter by status

Filter by category

Identify yourself with your email address

Increase the number of events and be able to filter by event under the Diagnostic tab

As an Admin , i would like to extend the permission to manage the app to normal users (add mapping)

2 Salesforce connections can escalate to same issue type on one JIRA instance

As a user, I would like to have all mapped fields go back to being clear when unlinking associations

I want to be able to map Jira issue types to multiple obejct types as in the new Connector

As an User, I want Salesforce Rich Text field (HTML) is compatible with JIRA Text field (Wiki)

Limit the JQL remoteObjects search for Jira issuess linked to SalesForce cases

As a user I need the ability to pull changes only to specific Jira issues

As a user, JIRA comments exceeding 4,000 characters should be trimmed accordingly (bellow 4,000)

Show Full name instead of username when mapping the Jira assignee field