Allow configuration of more environments with Jira integration
Johannes Liegl
The Jira integration is currently too limited, and they'd like to be able to configure it for more than one environment at once. They use Jira for everything, so being able to track all environments in Jira would be useful.
Log In
Johannes Liegl
Merged in a post:
Include Project Name in Jira Integration
Johannes Liegl
When using the Jira Integration and going from Jira to FME to create a new flag, customer would like to have the Project name passed over as well. Currently when sent to FME, the window opens up to create a new flag and the user can select which Project the flag should exist in from the drop down.
Customer is already having this information exist in Jira and would like to pass it through the integration so that users do not need to reselect the Project and can avoid human error of creating the flag in the wrong place.
Johannes Liegl
Merged in a post:
Multi-Environment Jira Integration
Johannes Liegl
Customer has many environments for their markets to adopt a feature flag via FME. Channel Delivery Managers (CDMs) manage their own feature rollouts in this way. Today, our Jira integration only allows for connection to a single environment, which blocks the CDMs from tracking their deployment progress in Jira independently.
Johannes Liegl
Merged in a post:
Expand Jira integration
Johannes Liegl
Jira integration currently only allows for a connection to a single environment, and doesn't do much other than basic functionality. The dev team and product team use Jira extensively and would love for the integration to do more. They're a small team and need as much automation as possible.
For example, the ability to connect to more than one environment. Also, the ability to create tickets based on filters (e.g. if the status is "100% released" create a clean-up ticket).
Johannes Liegl
Merged in a post:
Enhanced Jira integration
Johannes Liegl
Current Jira integration is too limited. They'd like to be able to do more with Jira, such as see the feature flag name, link to more than one environment, trigger automations (e.g. a clean-up ticket), etc. They built their own integration for now that works for this purpose, so it's not urgent, but this has been a pain point since their time with FF Classic as well.
Johannes Liegl
Merged in a post:
More robust Jira Integration
Johannes Liegl
Want it to be more extensive. For example, ability to update Jira story statuses, do a feature flag deployment from approval of something in Jira, auto-create clean-up tickets. Jira is a key tool for them, so this integration is important.
Johannes Liegl
Merged in a post:
Select Multiple Environments for Jira Integration
Johannes Liegl
Customer would like to be able to select multiple environments when setting up their Jira integration. Currently they can only configure the integration for one environment which means that in Jira they will only see that the flag is configured in one environment.
They have users that will not be in FME but will be in Jira so they want them to be able to more accurately see all of the environments the flag is configured in.