-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
Problem:
The current CSV import process merges the values of the Issue ID field into an "External Issue ID" field. This creates confusion and inefficiency in subsequent imports due to the difficulty in identifying unique ID values.
Proposed Improvement:
Implement two distinct import options: Stateless and Stateful Import.
1. Stateless Import ("Issue ID") - This value will only be used within the specific import process to link issues. This temporary ID is stateless; it does not persist beyond the current import session and does not conflict with any existing or future IDs.
2. Stateful Import ("External Issue ID") - This option allows users to map the ID from the source system. This ID maintains its state; it is saved in the system for future reference and can be used for mapping and tracking purposes.
Expected Impact:
The introduction of Stateless and Stateful Import options will enhance the efficiency of the CSV import process, eliminate confusion related to ID duplication, and simplify the process of mapping and tracking IDs from source systems.
- follows
-
JRASERVER-66150 Values mapped to "Issue ID" field upon import will be saved to "External Issue ID" custom field
- Closed