-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Summary
Provide a public Java API for updating the organization
Background
Renaming the organization's name is a lot of work. I would have to:
- remember the users in the organization
- remember the ServiceDesks attached
- delete the old organization
- create a new one
- re-add the users
- re-add the ServiceDesks
This is a way I would really not want to go.
Related tickets:
- relates to
-
JSDSERVER-4605 Create REST API to update Organization field
- Gathering Interest
- is depended on by
-
DEVHELP-1755 Failed to load
- links to
Form Name |
---|
[JSDSERVER-6045] Provide a public java API to update the organization fields
Labels | Original: cc-integration cc-integrations devhelp ecosystem rest_api | New: cc-integration cc-integrations devhelp ecosystem rest_api ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 976827 ] |
UIS | Original: 1 | New: 0 |
UIS | New: 1 |
Workflow | Original: JAC Suggestion Workflow [ 3012130 ] | New: JAC Suggestion Workflow 3 [ 3647498 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2858581 ] | New: JAC Suggestion Workflow [ 3012130 ] |
Reporter | Original: Anne Calantog [ acalantog ] | New: aponert [ andre.ponert ] |
Description |
Original:
h3. Summary
Provide a public [Java API|https://docs.atlassian.com/jira-servicedesk/3.9.1/] for updating the organization Related tickets: - [[JSDSERVER-4605] - Create REST API to update Organization field|https://jira.atlassian.com/browse/JSDSERVER-4605] |
New:
h3. Summary
Provide a public [Java API|https://docs.atlassian.com/jira-servicedesk/3.9.1/] for updating the organization h3. Background Renaming the organization's name is a lot of work. I would have to: * remember the users in the organization * remember the ServiceDesks attached * delete the old organization * create a new one * re-add the users * re-add the ServiceDesks This is a way I would really not want to go. Related tickets: - [[JSDSERVER-4605] - Create REST API to update Organization field|https://jira.atlassian.com/browse/JSDSERVER-4605] |
Remote Link | New: This issue links to "DEVHELP-1755 (Ecosystem Jira)" [ 390184 ] |
Problem occurs when the organizationID is used in other context (insight per example). And if we create a new one, we need also to reaffect all tickets. Thanks to add this feature in organizationService. Feature is available by the UI :