Tarun Sapra Community Champion

Hi Henning, Yes i have used REST API for such kind of work, i was looking for a more of "built-in" alternative...but anyways i guess would have to write some scripts :)

it's a must have feature indeed!

Then I would suggest you to use a 2 dimensional JIRA filter in your dashboard which uses the same JQL filter as your kanban board thus getting same list of issues - https://confluence.atlassian.com/jira064/adding-the-two-dimensional-filter-statistics-gadget-720416991.html

You can customize the story cards - https://jira.atlassian.com/browse/JSW-3922 and thus see assignee and story points on the same card. that seems to be the easiest way to me.

But then if your JIRA is so "Regulated" why don't you have a test instance of jira?

Please make sure your file is location on the server and the "owner" of the file is the same user which is owner of confluence application.

Just to add what Nic has already shared, I refrain from using names of custom fields in the JQL instead use "cf[1003]" i.e. the id of the custom field

From the docs "Once your plan is created you can change its name by clicking the plan name and changing it."

I was able to integrate github and jira by following the documentation https://confluence.atlassian.com/display/BITBUCKET/Linking+Bitbucket+and+GitHub+accounts+to+JIRA, few things to keep in mind 1) You need to generate cliend id and client secret and copy them in your dvcs plugin configuration one of the problems I…

For that please write a workflow post-function to create a branch in bitbucket, from the post-function of the workflow you can invoke a webhook which is basically a REST call to create a branch in bitbucket. 

Hi @ajay sikka, Please see here , this documentation should answer your queries - https://confluence.atlassian.com/adminjiraserver071/configuring-workflow-triggers-802592811.html Triggering branch/code commits/ merge etc during workflow transition.

You can only @mention people who have the right to view an issue. Thus, the user can anyway browse/see the issue only then you can mention him.

When you change the IssueType Scheme, the new issuesTypes are validated against the field configuration, so if the reporter if mandatory in the field condiguraiton that results in migration failing as the validation of the issueType with field configuration enforces the reporter to be present even on older issues which…

Hi, You should click on retaining reporters and assignee otherwise you would loose them, this happens if the new field configuration scheme has reporter required and the old reporter no longer has permission to be the reporter anymore. To be honest, I don't like the whole IssueType migration process, I have lost some data…

I don't think there would be any problem in adding dummy email except from the log files (atlassian-jira-outgoing-mail.log) being filled with error, if you choose an option of sending an email to all the newly created users.

The new email sent to the user will be picked up by JIRA , delete the email and JIRA will add the content of the mail as an comment to the existing ticket. It's always a better idea to use a dedicated mail account (not a user account ) for these purposes. There are some plugins out there using which you might be able to…

I don't think it's easy via behaviours plugin to change the context, sure it can change the value of the custom field within the same context but not the whole context.

Hi Andreas,I hope you are not running into this issue - https://jamieechlin.atlassian.net/browse/GRV-383 ,

Hi Thomas, Did you get it fixed?? You have mentioned - " * In JIRA -> System -> Services there is no entry from script runner (I remember seeing them there before 3.0)" But the escalation service is located in the "Built-in" script section of the script runner plugin -…

has you issue been resolved?

Here is your answer - https://answers.atlassian.com/questions/156863 Make sure you have assignee field on the edit screen of the issue.

From the docs - "The simple way to update an issue is to do a GET, update the values inside "fields", and then PUT back." Thus do a get request and then then a put request with the same json data and just modify the "assignee" filed to a proper user ID , "me" isn't a userId it seems which you are doing right now.

See here - http://stackoverflow.com/questions/19671317/400-bad-request-http-error-code-meaning Make sure your JSON is per the API specs

Make sure you are part of "site-admins" group on cloud, if it still doesn't work just raise a ticket for support.

If you have admin rights then fo to "System (top right)" and then search for "External System Import" and then select CSV. Shortcut for this is just press "g" twice in quick succession and type "external system import" If you don't have admin rights then on the top banner you would be seeing "Issue", when you click on…