RELATED IDEAS
Allow parking lot features and releases to not be sent to Jira
I use the parking lot to prepare for my upcoming releases thus the release name is not in Jira. These are also stories that do not need to be in Jira yet. With integration turned on I get an error every time I move a feature around in the parking lot due to it trying to send the release information to Jira which does not exist there.
-
ADMIN RESPONSEOct 25, 2018
Thank you for your idea. Currently features will not be sent to Jira until you say so -- using the Send to Jira option in the feature detail. The errors you are seeing are most likely caused because the feature was previously linked to a record in Jira. Deleting the link will resolve the issue. You can then resend it when you are ready.
© 2024 Aha! Labs Inc.•All rights reserved
I don't think the admin response is a complete answer. For example, if I move a feature from the roadmap to a parking lot release, due to re-prioritisation, then the integration attempts to create the parking lot release within Jira. This isn't desired as the parking lot releases don't relate to a version, but rather to a set of priorities.