Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! You do not "simplify the workflow" by changing workflow schemes. It's a whole different approach. It is done from a board point of view rather than a project (projects are configured with schemes) Go to your board and have a quick look at the board filter to see what projects it might be…

It's not strictly a "bug" - sub-tasks are not sprint items and they don't have a sprint field by design. It's actually working as intended! However, it's not intuitive, it's not helpful and it's not good for us humans. If you ever run into a server install I used to be an admin of, you're likely to find a handful of…

Ah, thank you, that's sorted out my confusion! Have a look at https://library.adaptavist.com/entity/set-behaviour-multi-and-single-select-options-and-value - I think that does what you are looking for!

I don't understand, now that you've said you're looking at two separate places to do this. What do you want from your "integration"? I am guessing that you mean you want to write something that draws a graph in another application. In that case, you don't need plugins or libraries in Jira, you need them in the other…

This gadget is not part of a standard Jira install. Do you mean the one from "great gadgets"?

Changing the workflow setup of an existing project is not something you want to code for - it is a LOT of work, you'll need to do all the checks for change of status and step in the os workflow stuff, migrating the issues and you'll need to fail the process to ask the users if there are migrations needed.

This is probably a bad idea because of the way apps are loaded into the Jira framework. What problem are you trying to solve with this idea?

If you don't want to reassign it, then just leave it. It's not doing you any harm, there's no need to blank it out.

Yes, but with a hint of "no". If you are talking about the actual server licence for each service, then no, the separate services won't care. You can move Jira to DC tomorrow and it won't care if Crowd, Confluence, Bitbucket and Bamboo are still on Server licencing, and nor will they. The "no" part is the applications and…

Welcome to the Atlassian Community! Can you tell us what the error message is?

What errors are you getting?

and, um? A title that tells us nothing followed by a screenshot of something that does not match it, with no other information is not going to get you any response. We don't know what you're asking.

No, the whole point of that app is that you undo everything you did in the transition. It's not there for editing data.

Sorry, I thought you said you were having the same problem as the original, but I misread it. You say you're not having issues go to the next sprint if you close the sprint with them in the last column on the board, which is the correct behaviour.

Welcome to the Atlassian Community! You need to bear in mind that just because a field is not on any screens, it does not mean it is not in use. I regularly created scripted or calculated fields to help with reporting that don't need to go on a screen.

Welcome to the Atlassian Community! I've seen Jira used for this, more than once. Each book is an issue, the workflow handles where the book is at the moment, and the fields the detail.

One way to get "unknown user" is to delete someone from your user directory - Confluence will display "unknown user" when there's no name it can look up (this is one reason we recommend disabling leavers, rather than deleting their accounts) That only applies for looking at the history though - a deleted user can't get in…

Welcome to the Atlassian Community! There is no "undo transition" in Jira, so I can't really help you. Can you explain what you mean by "undo transition"?

Yes, you do that at the operating system level though - you need to set up something that can monitor it and issue a restart command. However, this would be "plastering over the cracks". It's the wrong thing to do. If your service is stopping without you telling it to, then you should be investigating that, with a view to…

Welcome to the Atlassian Community! I am sorry, but your question is not clear. What "URL name" are you looking to change? The base URL of the system (in general admin) or the URL the service resolves to (which you would have to change in your networking settings) Or have you mis-labelled this question with "server" when…

Why would you need to stop people using it for a time?

There's nothing in those docs about "site access" beyond saying "you can give access to people you want to use your site (i.e. the products that form the site)" I think you are misreading what "site admin" means, not site access. A site admin can grant people permission to use the products and the permissions within them…

Not my fault Atlassian have rearranged their docs

I can't see what you are doing here, a screenshot of a rule box that's nothing to do with the current transition does not tell me a lot. I can't tell you more than you need to be adding a rule to the workflow.

Welcome to the Atlassian Community! Product access is site access. An Atlassian site is made up of one or more products. There isn't a site outside them. If you were to separate the site access from the product access, you'd find people with site access have nothing to look at. What are you looking for people with "site…

Look at the workflow. An Automation can not transition an issue to a new status if there is no transition between them in the workflow, or there are blocking conditions on the transition (not automation conditions, workflow conditions)

Nothing. Burndown measures what you saiid you would do against what you did. There's no looking at partial completions.

Welcome to the Atlassian Community! My guess is that an inexperienced administrator has added the resolution field to the edit screen. This is something you should never do, but I'm afraid Atlassian have never coded to stop us doing it (not even a warning), or written much into the docs, so it is a really easy mistake to…

No, it will still do that. But no one should be changing issues that are done. It makes no sense to log work against issues that are complete and need no more attention.

Welcome to the Atlassian Community! Jira only creates some of those issue types by default, and some apps you can add to it will create some more. Of your list, only Bug and Epic are Jira issue types. I would guess that some of the ones with "Test" in their name may have been created by a test-management app. There are…