Versions Compared

Key

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

 

Table of Contents

When processing an email via a Profile and its Project Mappings, the default evaluation of those rules is 'first match wins'.  Its also possible to change this strategy to a rule-priority based approach.

...

  1. Review the Profile with the Rule Evaluation Strategy of First Match Wins, click Edit:

    Image RemovedImage Added

  2. Select Priority Rule Evaluation Strategy, and hit Submit:

    Image RemovedImage Added

  3. See the result:

    Image RemovedImage Added

  4. With the Rule Evaluation set to Rule Priority all Rules now get a Rule Priority value that determines evaluation order.  Review the Project Mappings, see them indicate default priority:

    Image RemovedImage Added

  5. In this example there is an existing domain rule, but we'll create a higher priority rule for sender boss@localhost that will win against the default.  In this case, we'll customize the issue created to have a priority of Blocker.  To do this, edit a Project Mapping (here the TEST project mapping):

    Image RemovedImage Added

  6. Then go to the Rules section and click Create:

    Image RemovedImage Added

  7. Create a new rule, setting the From: regexp to be boss@localhost:

    Image RemovedImage Added

  8. Now, to indicate that this rule has applied, we customize the Rules properties, note that the Evaluation order of rules can be changed, just as it could with 'First Match Wins'.  Potentially, this allows high priority rules to be evaluated sooner.  Click the cog icon to configure the rule:

    Image RemovedImage Added

  9. From this point, everything can be configured, see the available sections indented under the Rule.  To set the priority, select the Issue section:

    Image RemovedImage Added

  10. (NOTE: many fields are inherited from the parent Project Mapping, and in turn from the Default Project Mapping).  Click Edit:

    Image RemovedImage Added

  11. Select the Blocker issue Priority, (if 'Non' is the value defined through inheritance from the Default Project Mapping, then the JIRA default will apply)

    Image RemovedImage Added
  12. And Submit, to see it overridden:

    Image RemovedImage Added

Validate new Project Mapping Rule

...

4.The value that caused the match

...

 The  The important thing here is what Rule applied, (3) above shows .*@localhost which is a general match for <anyone>@localhost.  It won because that rule had a default priority, and the other rule for boss@localhost also had that priority, ie, it was no better.

...

Filter by label (Content by label)
showLabelsfalse
max5
spacesJEMHC
showSpacefalse
sortmodified
showSpacetypefalsepage
reversetrue
typelabelspageproject-mapping
cqllabel in ( "project-mapping" , "rules" ) and type = "page" and space = "JEMHC"labelsproject-mapping
Page Properties
hiddentrue

Related issues