Hi,
We're using the function in JEMH: Profile->Config->WorkFlow->onComment advance from States, in order to update a custom field that is used as a flag.
When an email is sent at the first time, the flag on the issue that was create is being updated, eventhough it's not commented.
What is trigering the comment event?
We need it to work only on comment, but it happens also on create.
How can we prevent from it to happening?
Hi Moran,
> We're using the function in JEMH: Profile->Config->WorkFlow->onComment advance from States, in order to update a custom field that is used as a flag.
How/when are you updating this field? I has as JEMH currently has a two phase issue creation process, resulting in ISSUE_CREATED firing for issue creation with core parameters set, secondly, a custom event fires after all the custom fields and attachments are added. This may impact your method of setting a given custom field.
>When an email is sent at the first time, the flag on the issue that was create is being updated, eventhough it's not commented.
The check will occur every time a message arrives, if the issue is in a given state to do so. Have you defined the restriction onComment advance from States value, to be the initial issue state, eg 'Open'?
As the entry above is text, its also possible there is a workflow transition collision, in which case, try using the numeric id of the step, some examples/background:
- https://thepluginpeople.atlassian.net/wiki/display/JEMH/Reopen+an+Issue+On+Comment
I think I didn't explain myself so good.
What happens that when receiving a new mail for the first time, the comment event is being fired.
We have a circle transaction: User Commented that fires from the JEMH-onComment advance from States from the In Progress transaction back to In Progress. That should happen only when an email is replied - On Comment, and not when an email is sent at the first time.
We don't want it to fire the transaction on Create, we want it to be fired on comment.
I attached here a screenshot of the profile-workflow configuration.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Right, so as I said before:
The check will occur every time a message arrives, if the issue is in a given state to do so. Have you defined the restriction onComment advance from States value, to be the initial issue state, eg 'Open'?
Really, the best place to continue this is in a support ticket, where you can attach your profile XML, your workflow XML?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I attached our workflow XML and the profile XML.
Hope that helps.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
attached where? Have you created a support issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I attached it here, but I guess it didn't work.
You ment to create jira in the jemh pluginpeople site?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yup, best place for tracking specific issues that are not quick answers.
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.
Hi Moran,
As per my understaning please mention issue key in email subject and comment as a email body on existing issue.
Regards
Onkar Ahire
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The issue key is mentioned in the email subject and in the comment subject.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.