I have an on-going sequence of test cycles and I want to write a query with a wildcard to capture any bugs in the test cycles without having to list the full name of each label.
Below is an attempt to use a wildcard for label TesE2E_CycleX, where X is one to many and will continue to increase:
Query:
project = pp AND (issuetype = bug) AND labels in (TestE2E_Cycle"*") AND type = bug AND status not in (canceled, done, completed)
AND priority = blocker
Note, the query above produces the following "Error in the JQL Query: Expecting ',' or ')' but got '*'. (line 1, character 68)"
The query below is currently in place and is inevitably getting larger and larger:
project = PP AND (issuetype = Bug AND labels = TestE2E_Cycle1 OR labels = TestE2E_Cycle2 OR labels = Test_E2E_Cycle3 OR labels = TestE2E_Cycle4 OR labels = TestE2E_Cycle5 OR labels = TestE2E_Cycle6 OR labels = TestE2E_Cycle7 OR labels = TestE2E_Cycle8 OR labels = TestE2E_Cycle9 OR labels = TestE2E_Cycle10 OR labels = TestE2E_Cycle11 OR labels = TestE2E_Cycle12 OR labels = TestE2E_Cycle13 OR labels = TestE2E_Cycle14 OR labels = TestE2E_Cycle15 OR labels = TestE2E_Cycle16 OR labels = TestE2E_Cycle17 OR labels = TestE2E_Cycle18 OR labels = TestE2E_Cycle19 OR labels = TestE2E_Cycle20) AND type = Bug AND status != CANCELED AND Status != Done AND Status != Completed
a) Use bulk-edit from the issue navigator (your agents will need to be granted the global permission to use bulk edit)
b) In what context?
c) It depends on the mail handler settings. The ones in JIRA Core have some configuration settings to look at, and the handler for Service Desk mails is a little different. But, I'd want to look at the requirement properly first - why are you wanting to filter and ignore these emails? A Service Desk is there to handle incoming calls, not silently drop them. Maybe if you could explain the filter for us, we can tell you more.
d) Define "unreadable" - it's often the mail client that messes them up by trying to be "clever", but it's worth explaining what's wrong with them, as it might be other things
Thanks for the quick reply!
(and sorry for my rather adverse request title: 'select multiple')
a) We found the rather hidden "bulk change" feature ... which solved our initial request!!! Thanks => SOLVED
b) Dragn' Drop would be useful:
c) Issues/tickets should only be created for specific mails ... obviously we first have to further check our current filters and mail-server settings. (Sorry!)
d) If customers (using e.g. ANY version of Outlook) reply to emails generated by the "Service Desk" the resulting HTML is completely unreadable in EVERY other mail-client/browser:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
b) Ok, you can't do either of those, I'd raise them (or find and vote for) over at https://jira.atlassian.com
c) Yes, I was thinking it might be better to do this on a mail-server side - JIRA's handlers would need coding and business rules and would still be a little inflexible. With a mail rule, it might be easier on the mail server to set up something like "accept this for JIRA if it matches this rule, otherwise reply with some form of sorry this mail will be ignored" type thing.
d) I'm not seeing this issue with any of the SD mails I get (ok, maybe the ugly, but it's correctly formatted, and I just find all email ugly), although I rarely use Outlook. The html looks fine in mail, gmail and rainloop. Maybe a screenshot?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.