Nic Brough -Adaptavist- Expert

A Cloud Jira install is created in a data-centre as near as possible to your initial access location (the algorithms don't always work, or take account of when you may have a sign-up from one region despite most of your people being in another) There is no "location of an app install". If it's an app that runs on the Cloud…

Could you give us the context of this? What is unity and what does it have to do with Atlassian stuff? 

I'd automate that with the Jira Cloud REST API 

What do you mean by "Pipelines for Jira"? What are you looking at there?

To answer the bit about generalised documentation, the Atlassian docs are mostly quite good at this. Take for example https://support.atlassian.com/confluence-cloud/docs/insert-the-jira-issues-macro/ - that is, as you say the "latest" doc on the subject and it's for Cloud. Look to the top right of the body though. You'll…

>it's including issues from other boards Yes, it will, if your filter includes those issues. Boards are not containers for issues, they are a view of a selection of issues. For any given board, if it selects an issue, it shows it. You say >list issues from one particular board Very simple - you use the same filter that the…

There's a bit of history of architecture in this question, which I'd normally not bore you with, but here it's helpful in framing the answer. With Jira Server, and hence Cloud "Classic" projects, Jira had a simple hierarchy of "Issue" and "Sub task". These were not the issue types, but a classification of the types. If you…

Start with a read of https://confluence.atlassian.com/adminjiraserver/jira-applications-installation-requirements-938846826.html Then for some numbers, head over to https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html I would not recommend reading the second until you've read the main part of the…

>is add the new Issue type as a separate Field Scheme? No, but you've used one of the two terms that tells me you're in the right area. There are two main layers to this. 1. The issue type itself. Issue types are a global list, so you just add "ops request" as the first step. However, that does nothing other than make it…

You'll need to define what your organisation wants from its "job aids" - my understanding of the term is that they are guides for doing things for your organisation. You don't get generic "job aids" because they're supposed to support your processes and systems.

During hot weather, I head for "cold and fizzy", which means: Option 1: But I don't have a sweet tooth, so almost all fizzy drinks are a total waste of time for me. I'll just about drink lemonade if there's no choice, and (rarely) a Dr Pepper because I have a taste for cyanide, but almost everything else is too sweet, and…

I see, you're asking about the "modular" nature of the Atlassian systems. They work on the idea that you get a core system that does the basics for a particular group of tasks and extend it when you need it. So Confluence is a wiki, but if you want question functions you add it. They do this because it's easier to…

You don't. The key is a fundamental property of a project, determining the unique identifiers for issues, and is the human-visible unique identifier of the projects. Could you explain why you think you want to hide it?

Dahsboards do not support arbitrarily inputs like that (yet) You'd need to rewrite the dashboard framework to allow for some form of input, and every gadget that used a filter such that it can recieve a variable and know how to handle it in when it's modifying the basic query behind the gadget. This is not a simple piece…

Check the permission scheme for the project, it controls who can log work, amongst other things. I would say it probably currently says "work on issue: Assignee" - I would probably add "role: developer" to it as that's the common way I see people flagged as developers who get things done in a project, but you should set it…

I don't use smart values, but that looks like a bug in it.

Ah, ok, try something like https://library.adaptavist.com/entity/calculate-custom-field-on-issue-update

The most common pattern I see is to rotate at 2Gb and keep the last 5 alongside the active one. Pretty standard for Unix-like logs generally, not just Atlassian.

You can do it with Scriptrunner (other scripting apps might support both of my suggestions, but I really don't know of another app that does the first option) * Create a web panel that extracts and displays the data. You could put the panel almost anywhere on screen and it will not affect the issue or need maintenance. *…

You will need to subscribe to Atlassian Access as above.

How are you putting it in? Code? Typing? REST call?

Nothing to forgive, it's a perfectly good follow up question, especially as I've made a mistake! The script we've pointed at is indeed for a scripted field. I only glanced at the top bit of it to confirm it was code you might find useful, and assumed it was a post-function that set another field. It's not, you should…

You can probaby tweak https://library.adaptavist.com/entity/calculate-the-working-days-between-two-dates a little bit to get it out. Personally, I'd do it as a "scripted field"

We have no idea, it's your data.

I'm afraid it is not the right place. This is the Atlassian Community, loads of people with an interest in Atlassian, but not necessarily your admins. They might be active here, but most of us don't know of them and they may not see this question. I know Mojang uses Jira and Confluence, but I'm afraid you've clicked on a…

No, it's disabled on Cloud.

Still, no drop-down there, I'm struggling to see what you are talking about.

The resolution field will always be shown on issue view. There's no good reason to hide it, as it's an indicator of whether an issue needs attention or not (and when not, it's telling you why the issue no longer needs attention)

We can't tell you what your company standards are - we don't work there. I would strongly recommend that you a) ask your company what their policies are and then b) implement a log-rotate service that will kill off older ones

If you remove a group from AD, that will be updated next time Jira runs a sync. You can check the user directory list to see how often the sync runs, and also if the directory is read-only on the Jira end. But be aware that you can tell Jira that a directory is read/write while being read-only on the directory side. You'll…