Nic Brough -Adaptavist- Expert

The live plan is to stay long term, from what I've heard.

I work for Adaptavist, so you should not be surprised that I'd recommend using ScriptRunner for this. But there are others - Backbone and Exalate can both do synchronisations between projects (less coding too). I think it's possible with Automation, Autoblocks and Powerscripts as well, but I've not tried them.

Only if the board filter refers to them. Look towards the top right of the board for the configuration options for it. You'll find the filter in the first tab.

Have you tried reading "see how to generate an error report" yet? What does that tell you? And please stop being so rude, it's not going to get you much beyond a ban.

Please stop SHOUTING, it is hard to read and rude. You need to tell us what errors you are getting. In English or at least with text we can put into google translate.

Why are you running maintenance plans?

It should be possible to edit filters with SR, but I don't have any code for it myself.

No, an issue can only belong to one project. You might consider having a second issue in the other project and linking the two issues together, then use one of the scripting, automation or synchronisation apps to apply change from one to the other.

You are getting an error in something you have written to look at a Confluence database. I am asking why you have written this and pointing out that you should not be looking at the database.

You are on Cloud, so you will be upgraded when Atlassian roll it out to your service.

Are you logged in? Have you asked your admins to check your account is in the right roles and groups etc?

So you'll need to look at the workflow to see where there are transitions into the status, and what conditions are on them.

Where? In the request or the issue?

A bit more advanced than you need, but you can just drop the bit about following links - https://library.adaptavist.com/entity/calculate-the-sum-of-all-values-of-a-custom-field-in-linked-issues

Why are you doing this? You shouldn't be even looking at the database.

Boards are not containers of issues, they are a view of a selection of issues. You'll need to change the board filters so that they only select the issues you want. I'd guess each one needs a filter like "Department = xxx"

That sounds like your workflow does not have a transition from the current status to "waiting for customer". 

You'll need to write some code to do that (probably in one of the scripting or automation apps)

Updated holds the date the issue last changed, not just when the status changed. Try using the "changed" operator with "status" - https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-operators-reference-939938745.html#Advancedsearching-operatorsreference-CHANGEDCHANGED

There's no way to do that on Cloud.

Atlassian do most support via help-desks, as those tend to be faster for the clients and cheaper to run than giant call centres pushing up the cost of the software. Telephone support is only available for premium customers (but if you go through standard support and get to a point where a call is most effective, they will…

There may be other errors in the logs that say "unable to read" about the database, but the way to check proprely is to get into it with a command line. http://www.h2database.com/html/tutorial.html is a primer for that. You'll probably need that if it is fixable too.

Not sure why you say "auto generated" as when you set up a Cloud site, it takes the name you choose. You can either buy a new one and export from the old and import into the new, or you can raise an issue with Atlassian support (https://support.atlassian.com/contact ) and get it changed. They won't do this often, I think…

13 will be counted because that's what you recorded. Generally, you should not be doing this though - when you estimate a story, you are kind of expected to include some allowance for bugs being found and fixed as part of the story.

One of the important things in the home directory is the index. If you lose that, searches, reports and most of the rest of Jira will fail to find anything. It'll all work when you create, edit or use the plain issue view, but anything that requires a lookup of most sorts will fail. TLDR: run a full locking re-index

Ok, but that doesn't tell us what you want to do with the strings you're going to get, or whether the names are currently versions or components.

Start at https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/ for the authentication (password) basics, and then move on to https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/ and the documents around it for what to post to Jira to get it to create an issue. For the email…

So, trying to help after that, what does the error report say when you follow the guide on how to generate the report?

Everything you have written since my last comment is rude. * You're SHOUTING at us * You're not bothering to read any response * You are refusing to answer any of the clarification questions I've asked * You're not seeming to read anything I've said * You're repeating stuff we've already told you gets us nowhere * You're…

It was mostly a guess, but the unfamiliar name of the field lead us down a route that got to it. I'm glad the (rather vague) pointer got you a good answer!