If you automate certain tasks in JIRA with help of scripting, then the

1.	If you automate certain tasks in JIRA with help of scripting, then they stop working in different environments due to change of IDs. What is a reliable solution to fix this problem?
Answer» The BEST solution is to reference objects USING names instead of ID. If this cannot be done then, we have to make the IDs same across environments. This can be achieved by following these STEPS: CHANGE the DEV environment as per your need and IDs Finalize the script Use project configurator and transfer these changes to PROD Copy PROD DB to DEV

If you automate certain tasks in JIRA with help of scripting, then they stop working in different environments due to change of IDs. What is a reliable solution to fix this problem?

Answer»

The BEST solution is to reference objects USING names instead of ID. If this cannot be done then, we have to make the IDs same across environments. This can be achieved by following these STEPS:

CHANGE the DEV environment as per your need and IDs
Finalize the script
Use project configurator and transfer these changes to PROD
Copy PROD DB to DEV

Discussion

No Comment Found

Related InterviewSolutions

If you have retrieved the create meta or edit meta of your project and the field that you are trying to analyze may not show up in resulting JSON then what does it mean?
What actions are currently supported in the JIRA advanced fields?
What is the reason for this type of error and how to fix it? The custom field 'XXXX' in the backup project is used by issue types 'AAAA, BBBB' but the field with the same name in the current JIRA instance is not available to those issue types in this project.
If you automate certain tasks in JIRA with help of scripting, then they stop working in different environments due to change of IDs. What is a reliable solution to fix this problem?
How do you perform health check on JIRA Confluence?
What global settings must be exactly same between 2 instances of JIRA while importing and exporting?
What all is not supported by the import and export plugin of the JIRA?
During import of configuration XML, if there is an error about orphan fields then what is the best way to handle?
While importing configuration file, if we receive following error then what is the root cause: “Load failed for reason: Missing a FieldLayoutItem for FieldLayout XXXX and field YYYY”?
What are the most common errors in exporting configuration data in JIRA?

If you automate certain tasks in JIRA with help of scripting, then they stop working in different environments due to change of IDs. What is a reliable solution to fix this problem?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment