search

serenity-bdd / serenity-jira

14 stars 27 forks source link

JIRA custom JQL #76

Open ghost opened 7 years ago

ghost commented 7 years ago

Currently when i get requirements it pulls all the project requirements from JIRA; even for backlog. I have declared my issuetype as story and project as my JIRA project. Can i add further filter on other fields? such as Sprint, fix etc.

I am looking to define my own custom field.

peterbecker commented 6 years ago

We are facing a similar problem as we have one JIRA project with multiple components, all of which are tested in independence. This means I need to filter on the Components field to get the set of tickets relevant for a test run. We would require either custom JQL or explicit support for the Components field for the two-way integration to work for us.

msc-consults commented 6 years ago

Hi, I too am experiencing this same problem.

Whilst on the topic of JIRA integration... is it possible to tag a JIRA ticket at Scenario level rather than at Feature? What about Tagging at EPIC level, is this possible?

MichiHC commented 5 years ago

Hi I have a similar problem as well. Is this feature going to be implemented?

Or is it possible to configure the used Jira issue types within the properties file? We use issue types Epic, Story, Bug, Architecture and Infrastructure. All the issues are now requirements, but i don't want to use infrastructure as such.