Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When creating a Profile, the Profiles configuration is the default Project Mapping that applies by default when no other Project Mappings rules are either defined or match, as such, the default Project Mapping has no rules.

...

Rule Driven Project Mappings

When additional Project Mappings (for a given JIRA Project) are created, it is then possible to add Rules of several types that cause this Project Mapping to apply over other Project Mappings or the default.  When Project Mapping Rules are defined, for the most part, fields defined in the 'Default Project Mapping' are inherited by but can also be overridden by additional Project Mappings.

...

Rules can further override values defined in the related Project Mappings, allowing very flexible issue creation with full access to all issue parameters at that time.

Scenario 1 : Create a Profile

...

Create a basic Profile

  1. Create a Profile:
  2. Defining the catchemail address of your inbound mailbox, the target Project, and the IssueType:
  3. See the new Profile, configuration of which is through the cog icon, it can also be copied the + icon, as well as exported (useful for support!) and deleted.
  4. A summary of key information in the profileProfile, indicating defaults, can be seen by expanding the Catch Email Address
  5. Use the Cog Icon to access the Profile, from here it is possible to edit some profile top level settings (1), and to gain access to the Project Mappings (2).
  6. Accessing the Project Mappings will show just the default Project Mapping, the lack of rules is shown by .  Configure the Project Mapping via the cog icon:
  7. The Profile view shows the vertical nav that will take you to specific sections of the Profile, in the main panel view are summaries of each section, with a Pen icon, which also takes you to the edit view of the section:
  8. To reinforce the 'default' nature of this Project Mapping, access the Rules link from the vertical nav:

...

  1. Create a Test Case:
  2. Whats shown next is the platform neutral standards based format for a simple text email, select the profile created above (1), then  set the From: smtp address (2) to be something valid, and the To: address (3) to be the Profile catchemail address.  From this screen its also possible to upload (4) a previously exported email (in this neutral TEXT format, not a proprietary binary .msg format).  Finally hit Submit to save (5):
  3. The Created Test Case can now be run against the Profile it's associated with:
  4. The Result of running a Test Case will show the Issue Key of the created issue, and some other info:
  5. As custom fields already exist for 'Email Sender Address' and 'Email Participants' the resulting issue would look like:

...

  1. In the Profile Project Mappings view, hit Create:
  2. Set the Project and give it a name, then hit Submit
  3. This Project Mapping doesn't yet have any Rules, so will never be used, indicated in the post-Submit view - .  Use the Cog icon to configure the Project Mapping:
  4. Here the TEST Project Mapping is now available for configuration, all fields marked  will without further change, automatically take on the value defined in the Default Project Mapping (by the way, this is to minimize the amount of configuration that needs to be done!).  Access the Rules section now:
  5. Initially, with no rules defined, again ... will Image Added will indicate the Project Mapping wont be used, so hit Create to define one:
  6. Rules can be created that match using regular expressions on the From or To (recipient) addresses defined in the email, as well as keywords, in this example, we'll map any sender from the @localhost domain with the regular expression .*@localhost (in regular expressions, * means any number of the preceding character not all characters, to match any character . is used, hence .* to match everything):

  7. After submitting, the summary for the rule is shown:

...

  1. Create a new Test Case with a From: address of example@localhost and a To: address of the usual catchemail (incoming mailbox) address.  To do this, create a copy of the Test Case that was made earlier, using the copy option to get going:
  2. Just change Change the From: address for this case to example@localhost and Submit
  3. After saving, run the new Test Case:
  4. The Test Case post-execution result screen shows that an issue was created in the TEST project, and specifically, through the Rule:  Rule=Sender 'example@localhost' matches '.*@localhost'

 

Info
titleManaging many catchemails and mapping through Project Mappings

Its possible to use one Profile, with one Project Mapping per 'inbound mailbox', in order to do this, the top level 'catchemail' addresses must include ALL inbound mailboxes. The simplest way to do this is with email aliases to a common account, for example, we have "support@thepluginpeople.com" with aliases "jemhc-support@thepluginpeople.com, jemh-support@thepluginpeople.com, emq-support@thepluginpeople.com", with these aliases present all mail ends up in one mailbox, then the catchemail address can be an easy {{(.*-support|support)@thepluginpeople.com}}, then Project Mappings can be associated through a Domain rule matching the full actual inbound mailbox address.

 

Filter by label (Content by label)
showLabelsfalse
max5
spacesJEMHC
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("project-mapping","jemhc") and type = "page" and space = "JEMHC"
labelsproject-mapping jemhc

...