Tarun Sapra Community Champion

grrrrr... let me give it a try with a hidden global transition instead.

Yes add the mail hadnler "create issue and comment" and make that email the project email in the project settings page and make sure the mail that is sent to the 3rd party is by this email.

Yes add the mail hadnler "create issue and comment" and make that email the project email in the project settings page and make sure the mail that is sent to the 3rd party is by this email.

but here the mail handler is adding the comment which was basically the email sent by the 3rd party companies to that email address

Hi, I haven't used a plugin to do it, but it works in my project, when a 3rd party replies to an email that email body gets added as a comment in the issue. The email id of the project of the issues should be same as the email id of the mail handler (create issue/ add comment)

You have to choose the correct source or multiple sources to import the issues. You can create the filter for the i missing issues and also import that filter in the portfolio. https://confluence.atlassian.com/jiraportfoliocloud/creating-and-deleting-a-plan-828785200.html

Hi @Nigel Morse, yes ofcourse you can try it on the server version, see my answer below

As I mentioned in my answer, only on cloud not on server version of JIRA.

Backlog isn't possible with Kanban boards on server version. On cloud it's available in Labs feature - https://confluence.atlassian.com/jirasoftwarecloud/blog/2016/02/make-way-for-backlogs-in-kanban-boards If you are using server version then I would suggest to use two Kanban boards, one for backlog prioritizing and the…

Hi @Steve Eckard Rather than having a "Development" component, I would suggest you to have a "swimlane" instead which would contain all the issues from the Software project board. As component is something which you add to the issues thus there is no point in editing the Software issues instead you add a swimlane in your…

Step by step guide - https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email

Yes, you can do it, it's not very difficult to implement it. In the post-function of the "create" transition of the issue workflow you can add validations to check if the user belongs to the group which can create the task issues or vice-versa. There are plenty examples of this on this site.

If it goes down due to crash, then you need something like Nagios to send out notifications.

As mentioned in the comments on Adaptavist, this seems like a scripting issue, please share your script. Thanks.

You might be facing this issue - https://jira.atlassian.com/browse/JSW-14871

if you find my answer then please accept /upvote answer. thanks!

JIRA Misc custom field is your solution - you can create custom field and add that field to screen and that field will have the value of datetime for any state you want, either when issue enters first time or last time! https://innovalog.atlassian.net/wiki/display/JMCF/JIRA+Misc+Custom+Fields

Yes, thats the approach to create groups and add persons in that group. Generally adding individual users to notification scheme is discouraged as that user might leave the job and his username would be inactive thus it's always better to have groups in notification scheme.

Currently, there is no way in JIRA for customization of notification scheme for a single User.

You can write a Transition post function script for this using scriptRunner plugin.

Currently Bitbucket doesn't have restrict permission based on SSH keys http://stackoverflow.com/questions/34326735/limit-access-of-github-or-bitbucket-repository But you can also look into read-only access based on Deployment keys- https://confluence.atlassian.com/bitbucket/use-deployment-keys-294486051.html

Sub-task's story points will not show up in the Burndown chart because of reasons on how JIRA Agile supports Agile implementation and it enforces certain good practices which include using story points for story type and not for sub-task. Please read the answers here - https://answers.atlassian.com/questions/216148

I am using JIRA 7.3, and for me when I add a "Done" issue in an version then in the Version report it shows in the graph" Scope change - Issue added to version" and in the report underneath the graph it shows the issue in the list of "Completed issue", this makes perfect sense to me. Since, when we add the issue we…

It was a crazy issue, the service was tryin' to execute a jelly script and the whole jira startup was getting stuck because of the jelly script, turns out that there was problem in the Single Sign on (firewall issue) which caused the credentials in the jelly script unable to log-in and thus the whole startup was stuck but…

i think Atlassian should have some config files for services ...it's very cumbersome to do it from DB

" turn the service off first" ? i can't find a way to do that without loggin in

If both are hidden I would suggest you to put the second transition in the post-function of the first hidden transition , it's a much cleaner approach.

Hi, I would suggest you to to use two different transition and the second transition can be hidden transition ( part of workflow transition plugin) and make sure the second fast-track transition post-function is part of this second transition which is hidden from the user and can only be triggered from within the workflow…

and if you have the script runner plugin installed, then try this https://jamieechlin.atlassian.net/wiki/display/GRV/Escalation+Service

Write a jelly script to automate it. Also, please provide more details https://confluence.atlassian.com/display/JIRA/Services https://answers.atlassian.com/questions/128176/how-to-configure-a-jelly-script-as-a-service Jelly Scripts run periodically and can do pretty much anything you want to do with issues.