When an incorrect jiraUser is first provided, a cookie is created that persists across subsequent requests. Even if the jiraUser is corrected, the system continues to use the outdated cookie, resulting in ongoing errors until the cookie is manually deleted. This behavior can lead to significant time loss in troubleshooting, as was my case.
Steps to Reproduce:
Initialize a request with an incorrect jiraUser.
Observe that a cookie is created.
Correct the jiraUser and attempt a new request.
Note that the system still throws an error because it continues to use the initial cookie.
Expected Behavior: When the jiraUser is updated, the existing cookie should either be invalidated or updated to reflect the correct user data, preventing subsequent errors.
Suggested Fix/Improvement: Mention this behavior in the README as a known issue or provide guidance on handling cookies in case of jiraUser updates to avoid errors.
When an incorrect jiraUser is first provided, a cookie is created that persists across subsequent requests. Even if the jiraUser is corrected, the system continues to use the outdated cookie, resulting in ongoing errors until the cookie is manually deleted. This behavior can lead to significant time loss in troubleshooting, as was my case.
Steps to Reproduce:
Expected Behavior: When the jiraUser is updated, the existing cookie should either be invalidated or updated to reflect the correct user data, preventing subsequent errors.
Suggested Fix/Improvement: Mention this behavior in the README as a known issue or provide guidance on handling cookies in case of jiraUser updates to avoid errors.