Nic Brough -Adaptavist- Expert

I'd use Confluence for that. You can make none, parts, or all of it globally available. A lot of places using Atlassian stuff have a series of spaces (by team or product) which you have to log into to use, and they document everything in those. Then when a doc is ready for the public, they copy the latest (possibly…

Ok, great. Well, the only way to have a developer consider UAT done is to have UAT and Done in the Done column. This looks confusing from the outside of the development team, but they're in a position where they can state that this definition of done is absolutely correct. I would then use a Kanban board, with the same…

I am a little fuzzy on how this might work, as I don't know your process or data, but if I assume: * You have a pile of projects, containing lots of issues, and people fixing stuff * An issue that is assigned to someone is eventually "resolved", and the assignee remains the person who either did it, or was in charge of…

The practical bit: Edit <jira home>/jira-config.properties (you may need to create it - it's not there by default. It's plain text) and add a line "jira.lf.date.relativize=false" to it. Restart Jira, you'll see all dates and times are now date based. I'm with you on the shortening of dates, it's just wrong. I'm relaxed on…

First, establish where the problem is. Is the board slow to load initially? Or is it when you drag and drop? Or it takes a long time or pop-up issue edit? Or when you save an issue? (or many of those). Is it the same pattern for everyone? Are there similar slownesses in other parts (or whole) of the system? Have you tried…

I think you may be in a place where you have no clear consistent "definition of done", which generally will not work. But there are a couple of odd things in your bullet points which are unclear to me and I'd like to question: I am going to assume you have one board that the developers are using to run their sprints. Given…

>Our goal is to develop a generic platform of features and to link them in part of the projects. Ok, but again, I do not understand what "part of the project" might be. >Is there an option to filter all features list and to see which projects they are linked to? Yes, search for "issuetype = feature" and the list of feature…

The first few lines of a log are generally enough to get us well into debugging. Exactly as you suspect, I suspect the script as well. But without seeing the script, we cannot do a lot more than tell you that there's something not quite right in its assertions.

The export file you get from Cloud is a couple of xml files compressed into an archive. As XML, yes, it's theoretically possible to build something that would search and interpret, but it would probably be slow and quite a lot of work to build, and a far quicker thing to do would be create a Confluence (server or cloud and…

Cloud does not really have username/password authentication available at all. The closest you can get is to use Atlassian Accounts for access, which are generally protected with username/password, but still are not really local to your system. (To do this, just don't use Atlassian Access or Google Accounts - the default…

It sounds like your custom plugin is not actually doing a transition correctly, but still managing to trigger a history update. Or it's doing the transition, getting to the point of history write and then failing the rest. How exactly does the custom plugin perform the transition?

Bear in mind that Organisation admins can only delete Atlassian accounts that are explicitly managed by them. If you are looking at a personal Atlassian account or one managed by another organisation, you can only disable them in your system, you can't edit, deactivate or delete.

A lot of people use de-activate and disabling an account interchangably. The basic idea is that there is a flag on the account that says "this account is inactive". Disabling/Deactivating an account * Means it can no longer log in * Means it does not count towards your licence * It can not be selected as new data in some…

The project is the first thing a human has to select for issue creation, as it defines what issue types, fields, workflow etc are chosen. I'm afraid there's no way to work out the project later - even if you could put it on screen low down on the create or even automate, you're in a place where people might enter data, and…

A mail handler is configured with project and issue type to create when email arrives for it. If you want different types selected for the same email inbox, then you'll need to find an app that provides an email handler that supports working out different issue types from the content.

Your "perhaps" is spot-on. Raise a bug/incident/sr/request and have all of them ask "which application?" along with the other fields you might want for each type.

Any form of view is a "download", so, unless you make the attachment completely unavailable, there's no "not downloadable"

You can do it on the board, if you've got swimlanes by issue, as then you're re-arranging them within their parent. Otherwise you'll have to go to the parent issue to do it.

>Jira should know to use the field value from my project for my projects automation. Correct? Actually no. Fields all belong to all projects, unless you have specifically limited their "context" to a sub-set of projects (or issue types) You'll either need to rename one of the fields, or go to Admin -> Issues -> Custom…

Request types are the way customers do "different fields by type". The issue type lies behind a request and is for the Agents to work with. The issue type is one of the things actually determined by the choice of Request (although the Agents can change it later)

If you're going via dbconfig to connect it to a database that Jira has already said is not empty, then it's not going to work - there's a reason it's complaining about a non-empty database in the installer and just bypassing the check is not solving the problem. I would be interested to see what is actually in the current…

If I understand the terms of usage, then no, this is not something you could do, each user should have their own account and hence licence. Would doing this cause you problems - yes, probably. There's some interesting side effects of trying to have a shared Atlassian account if you are using those for access. And if this…

There's one last long-shot - could you * Tell us what version of Jira it is (you mentioned 8.6 earlier, but I suspect you're now higher than that?) * Tell us what the database version is (not via Jira, but directly on the database command line (don't trust everything Jira is telling you!) * Confirm you're running…

There are some example validator scripts at https://library.adaptavist.com/search?term=validator

You do not. You have to put it on the view screen

Actually, that part has not changed, your searching landed you the right answer. The layout of the buttons and menu is still controlled by their "weight" in the property files embedded in the .jar files. So you'd need to unpack, tweak, re-pack (and bear in mind you would be unsupported and have to repeat on every upgrade)

Ok, great. That looks like it is now finding a single field and reading it. However, that field looks like it is returning a user object, not a collection of selected items. Can you confirm exactly what field type Teilnehmer is (and what its searcher is)?

No, creating a version is not done by moving issues into a project. But you can add a new version before you move the issues in, then edit the incoming issues to select that version for affects or fix (or custom version field)

Any Jira or System admin can delete screens. Go to Admin -> Issues -> Screens for the list of all screens in your system. You will find a "delete" option on the right for any screen that is not active in your system. You can't delete the ones that are in use, because they're being used. This list of screens includes the…

Sub-tasks don't appear on the backlog because that's not really what a backlog is for. You can only prioritise them within the issue of which they are a part of too, having them in the backlog wouldn't tell you much.