We are currently using a Google form to create bugs in Trac using a Python script called Email2Trac. I've been tasked with modifying that to work with JIRA so we only have one piece of bug tracking software. I can create issues, but have no control over what goes into them with the exception of the description.
I need to know how to format (encode, script, whatever?) the text in the outgoing Google email to create issues in JIRA with JETI, specifically how to designate Components, Summary, Description, Issue Type, Priority, Reporter, etc. I need to be able to have the reporter (who will most likely not be a JIRA seat owner, hence the use of JETI) on all emails back and forth.
I've tried using some of the things (Components, Priority, & Reporter) available in the templates, but they're just ignored and show up in the description instead of being parsed. I don't know how they're supposed to be encoded/formatted in the email. and none of the tutorials explain this (that I've found thus far). For example, in our current email system (Email2Trac), to designate some of the fields, I simply do this:
@reporter:email@example.com @component:someComponent @type:defect @priority:[level] @description:blah, blah, blah
Those all get parsed into the resultant bug in the places you'd expect them. I want to know how to do the same thing with JETI.
Can someone please post an example of what the outgoing mail for the JIRA/JETI configuration should look like. Once I have that figured out, I can proceed with modifying our current Google form to work with JIRA instead.
In JETI, you need to do the following:
Once you have a field rule for each tag, fields should be populated.
Well, or not...I've added more field context rules for @reporter and @priority and both are just being ignored. The reporter is being set to the default email that I'm sending to in my mail handler instead of the address I provided in the email, and the priority is just being set to "Minor" which is the default.
The email body looks like this:
@component:Online RMA @reporter:firstname.lastname@example.org @priority:Blocker
The only piece that's working is the `@component` part, the rest is not.
I've used the exact same regex as you provided for "@component" and simply switched in the appropriate field name, EG: (?i)@reporter:(.*) & (?i)@priority:(.*), set their issue fields appropriately, I've used sequential capture groups and matched their processing order to the capture group numbers. See screen capture belowimage2016-10-28 11:38:54.png
What am I doing wrong?
The problem is that your expressions for reporter and priority contain only one capture group, but the rules are configured with Capture Group 2 and Capture Group 3 respectively.
Please change both of them to Capture Group 1.
Read more on capture groups and regex: http://docs.oracle.com/javase/tutorial/essential/regex/groups.html and http://docs.oracle.com/javase/tutorial/essential/regex/index.html
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs