Haddon Fisher Expert

The only way I could see to do this using 'out of box' functionality would be to have a custom field for each variable, and then use something like Automation rules to stitch it all together on create. There are several plugins out there that would also allow you to do this; we use [this…

The out-of-box JIRA notification functionality is used for all issues in a given project, so if you need to use those for some reason, you would need different projects for each type. However you could build custom notifications using the newish 'Automation' functionality based on pretty much whatever you want.

Phew!!!!

I wouldn't think the type of field would matter much except how you access the info...What type of custom field are you storing the email address in? Have you tried {{issue.customfield.value}}?

Take a look at the issue using the REST API ("yourjiraurl.com/rest/api/latest/issue/[issuekey]") and see if it is storing the email address as a basic string or if there's something else going on? For example, if your custom field is a 'user' type field, the field is actually an object with a bunch of values. As example,…

You should be able to update the query which populates the board to do this, you would want to add JQL similar to: AND (resolution = empty OR resolved >= -2w) This will show issues with an empty resolution or those whose resolution date is within 2 weeks. 

Thanks for the correction @Jack Brickey , did not know that but glad to hear it!

Excuse the different names for statuses and the slight visual discrepancy, I am running JIRA server. I've added two things to your setup: 1) The second component makes sure that the issue being transitioned has an epic. If it doesn't, then there's no point in continuing. 2) The second component in the "For Epic" branch…

Bulk update won't work, since you are copying a value and not applying the same value across all of them. An export\import could work, but seems a little heavy. I am with @Jack Brickey re: Automation; use the 'Automation for JIRA - Lite' since it's free and has the functions you need to solve this very quickly: * Use the…

Before we get into customizing your notifications, you should know that they are configured at the project level, so whatever is set there will happen for ALL issues. Based your initial post that "when a ticket is submitted all people who are assigned to the project receive email notification" it sounds like you have a…

Unfortunately I'm not sure how you would be able to track this without using status, flag, or a custom field (plugin or otherwise)...those are pretty much the options :) You can use card colors to add a colored bar to the left of kanban\scrum cards based on whether the field is checked or not. I am not sure how it would…

The last thing a mail handler does when it processes an email is delete the message from the mailbox, so it would never live long enough to make it to the second handler. I have never used JEMH (suggested above) but the way I would handle this is: 1) Set up a rule for your mailbox which clones any inbound message and puts…

A check for the epic's status in addition to the child stories to exclude those specific edge-cases. 

I can't think of a way to do this using out-of-box functionality, but it would be a very simple Automation rule. 

What happens when you take the "Create Issue" component out of the "For Current Issue" branch?

Gah I'm sorry - I updated the wrong tab! Sorry :(

---Insert incorrect answer here----

The standard "assignee" field won't let you have more than one person, but there is a custom field type called "user picker (multiple users)" which would work.

Is your 'branch' component directly below the 'create issue' component? From the error it looks like maybe the 'create issue' is in an 'If' block it can't see into.

There's a ton of ways to solve this one, here's two: Uses Automation for JIRA * Create a checkbox field called "Blocked" with two options (Yes and No) and set the default value to "No". If they don't mind needing to click "Edit" to flag the issue as blocked, you don't need to set a default value. * Create a date field…

Go to "Project Settings" and then "Notifications" and see what is listed under "Issue Created". It sounds like you have a group or project role in there, when you would want just "Assignee" and "Reporter" (and maybe "Watchers").

Is there a need to use a script for this? If not, it would be trivial to build in Automation.

There's lots of different ways an application can be 'internal only' so this is really a question for your internal technology team. For example, if your internal JIRA server cannot talk to things outside of your corporate network, you'd need to either be inside that network yourself (and running Tableau Desktop) OR have…

Automation for JIRA is also an option.... Pro's Over ScriptRunner * Has a UI * Doesn't require scripting knowledge to maintain Con's * Yet another plugin * Not super friendly to maintain if you have a lot of mappings\possibilities

The piece I think you're missing is how to make links in markup: [some alias|some URL] Stringing it all together... [!some image!|^attachment.ext] For 'some image' I was able to use either an image URL or an attached image. 

Automation for JIRA is probably the easiest way to tackle this.

You said you are not using the 'parent-child' relationship between epics and stories; how are you establishing which epic a story is a part of? Assuming there is some kind of relationship between the two, you could use some of the JQL functions added by the 'Scriptrunner' plugin to do this.

Unfortunately I don't think this is possible. JIRA doesn't make the sprint start and end date available for display in dashboards (or nearly anything else) :(

I am using the JIRA Server flavor of Automation, so I am not sure if would be the same on Cloud, but there is a purple "Branch rule / related issues" component which has an "All Created Issues" option. If you put your "add watchers" component behind this, I think it would add it to the new issue and not the old.

Each JIRA mail handler can only make issues for a specific project\issuetype combination. However you can achieve what I think you are after using an IMAP mail server and some Outlook rules: 1) In the mailbox you have for this, set up a different folder for each project\issuetype combination you want. 2) Use Outlook rules…