Nic Brough -Adaptavist- Expert

The built-in copy script can only handle simple cases where the type of data in the fields is similar enough. A single issue picker going to a multiple issue picker is not supported. You will need to write your own bit of code to convert the data you extracted from the single picker field to the multiple-picker type.

Ah, you have "fielditis". There are too many fields with status in their name, and because of a poor design choice on Atlassian's part, they are obscuring the status you are looking for. Most of your status fields should be removed from your system and handled properly by sensible processes mapped to how you want to work.…

Going back to my picture - yes @Jack Brickey it's Wellingborough. 5 minutes walk from my house. I use it as an example of how people fail to look up - most of the locals have no idea it's there, I noticed it the day I moved here.

* It's not great to compare to null, you can just say "if there is a value" or "if there is no value" - in this case you can say the second with "if (!DOBValue) " * Where are you stuck on it? * If you want just the year, then change your script to only return the year, and change the output type to number or string - a…

I think this is a bit of a confused conversation. There are two types of "custom field" being discussed to my mind: * Custom fields for issues. These are configured (by Jira admins, with some delegation to project admins in some cases) at a project level, but act at an issue level - each issue may have data for a field. *…

This can't be done - the cascading-select list is a single field, so it has a single name, like other fields.

To enable bugs, cases, sub-tasks and so-on as sub-tasks on issues in a project, add the sub-task types into the project's "issue type scheme" However, bear in mind that the sprint estimates on sub-tasks will not be counted on a Burn chart because you do not estimate or burn on sub-tasks, they're not what you commit to at…

I think you got a good answer from Bastien over at https://community.atlassian.com/t5/Jira-Software-questions/What-is-the-process-to-acquire-and-apply-the-point-releases-or/qaq-p/1494496 - it's what I would have said too. Note that Atlassian sometimes (although not frequently) do "patches" rather than releases. These have…

The people section works with the permissions, it's not an "override". Permissions are a set of rules that say who can do what. Create issue, edit issue, transition issue, work with sprints, set assignee etc - all actions that can be allowed to accounts. The accounts they are given to are variable and dynamic - you can…

Your screenshot is of a Jira Service Desk Portal, which handle requests, not issues. These are configured in the portal settings of the JSD project they are part of, but there is not a lot of flexibility - you can change the logo, wording, and background image. If you want more layout options, you'll need an app like…

The [system] thing simply means that you already had an issue type with that name when you installed Jira Service Desk. It stuck [system] in there just to differentiate them. You can merge them (I probably would do that, but I do not know your data well enough to be sure its the right thing), or rename them, or delete one…

Versions are project artefacts. One of the things that this means is that you can't use them outside the project they belong to. Atlassian have some motion towards having versions that can be shared across projects, but the the current situation is that any version you put on an issue must be a version that belongs to the…

Multi-line text fields cannot be added to roadmaps as measurable data because they're not measurable. What metrics could you get from "The pen of my aunt is in the garden" to compare with "my cat's breath smells of cat food", for example?

It is very very obscure, I admit, but that's the challenge, right? The building is flanked by a couple of old coaching inns, one late 16th century and a larger one built in in the mid-1600's by a supporter of Sir Francis Drake and still carrying the name of "The (Golden) Hind". The House that Jack built is, obviously, 250…

So, assuming that there really is nothing else running on 7990, what is wrong in the properties file?

See https://developer.atlassian.com/server/jira/platform/database-schema/ But don't - the database is not suitable for reporting, it's the worst single way you can possibly read Jira data (and you certainly won't be using it for write). If you can tell us why you are asking this question, we can probably point you at the…

What do you mean by "target group is unhealthy for https port"? Is that an error message, a report from another system, or a translation that has not really worked too well? What have you done to reconfigure the ALB and Confluence to handle https? What docs are you following?

What's to clarify in "you need to read the log"? Log into the server and go to <bitbucket home>/logs - open the log file in a viewer/editor

What does "not working" look like? Have you followed the instructions for setting up Nginx as a proxy in full (as you've only given us a snippet of your Nginx config and not mentioned the other things you need to do, I would guess not) It's pretty much the same setup for Jira and Confluence in the proxy - see…

Use the REST API to read issues from Jira.

You will need an app like Behaviours to do this in the front end. You can't do it in the back-end at all, so REST users will always be able to bypass such validation.

There's no way to do this. Issue type is nothing to do with whether something can go into a sprint.

This looks to be a bug in the app you are using to provide OKRs. You haven't told us what that app is, so we're completely stuck, but I suspect we'd end recommending contacting the vendor anyway.

Projects do not have custom fields. Custom fields can only be done at the issue level.

What have you changed in Chrome?

In the file I mentioned in my previous comment.

Why are you using a date-time template? Your script is returning a string, not a date. Also, how are you triggering the recalculation you need to do every year?

Issues are not something the customer sees. Requests are for customer interactions (and have an issue behind them for the Agent to work with)

Start by reading the log at the time it stops.

Could you look at what tables exist in this database before you run the installer, then after it throws this message?