RELATED IDEAS
JIRA integration based on JQL query
Currently there is one option for selecting the items when creating an AHA!-JIRA integration, the JIRA project name.
In our system several teams are using more than one JIRA project so in this way we have to set dedicated integrations for each JIRA project.
Other problem is, that several teams, departments are using the same JIRA-s during the import we have to specify the needed items with a JQL. Otherwise after the import the workspace will be full with irrelevant features, items not related to the team, workspace.
I would propose 3 options:
Having an option to add a specific JQL at the "Select Jira Project" page beside the current Project and Board options
Enhance the board option in this page. The Project can't be mandatory in this case, and from the selected board not just the sprint information used, but all the items on that board.
Let to store and use saved JQL-s for manual import. And let to set saved JQL-s as default JQL-s of automatic import.
4
MERGED
Configure Default JQL by customer for development tool import
We’d like to see default JQL changed to :
resolution = Unresolved
or probably better yet, make this string configurable for an organization.
We use this step often, and we can’t use it as is – it has to be modified every time.
1
Shipped
3
MERGED
Customize "default" JQL query by project
We have customized our workflow in Jira and it would be helpful if I could establish a user-defined "default" JQL query for each product. Every time I run the import, I have to delete the default and replace it with my project-specific JQL query o...
1
Shipped
This would be really helpful. JQL can be added to refine manual imports via Jira that use the existing integration, but we're not able to apply this JQL to the integration itself (which is much more useful for ongoing updates).