Nic Brough -Adaptavist- Expert

Could you describe the exact behaviour of "will not take it"? When you click on the name in the list, what happens? Does it just jump to another selection and choose that, or does it accept it but never save it? Or is there an error message?

Is it greyed out? Or is the user the current assignee?

When you reinstalled, did you install Jira or Jira Software? Can you log into the new system and go to "manage applications" and check what is installed and licenced there?

"in backlog"? I think we'll need a screenshot of that, plus the full JQL of the swimlane you're defining and the issue view itself.

Ok. So, yes, if you use an Atlassian.net address, Atlassian provide the incoming mail service for that (they own the atlassian.net domain, so they can). If you want it to use another email domain, you are going to have to provide the email inbox for Jira to read. This means providing the mail server, and having a mailbox…

What errors are you seeing when you try to create the links between your server instances?

You will have to do it one by one (unless you're willing to completely destroy the target and get nothing but a copy of the entire source system). One trick that might help - consolidate your source spaces together, then de-consolidate after merge. 

You're using the wrong template for the output of the field. Return (double) should probably be going out through a numeric field.

I'd use the script from the library, adjusted to remove the -. After questioning the point of the requirement.

https://library.adaptavist.com/entity/update-the-value-of-a-custom-field-using-a-listener might be a really good base for your script I would recommend a look at * the requirement - I can't think of a good use for trimming out the - * using a "scripted field" instead - the script would be more simple because it becomes…

Test cases do not really map very well to Jira issues, they're very different things. I would recommend looking to one of the test management apps in the marketplace and letting that handle the issue types it might need. However, if you are going to stick to plain Jira, then it's Admin -> Issues -> Issue types -> Add

You'll need to use a different post-function. Copy field works by copying a field. It takes the new data and overwrites the old content. Labels (amongst others) is a field that holds a list of values (even if there's only one). Your need here is to be adding to that list, not overwriting it with another value. In the…

For the general configuration of an issue type, go to Admin -> Issues -> Issue type. Once an issue type is associated with a project (via the "issue type scheme"), it becomes a structural thing you can configure for the project, so that may be where you need to look to "reconfigure". That is done at two levels *…

You say: >we don't need to remove from create screen we just want if the status is open it should be in unresolved state You will need to make a decision. Either you want unresolved issues to be unresolved until closed, or you want the resolution on the create screen so that all your issues are created as resolved. I think…

Do you mean you want to re-configure what an issue type is? Or you want to change the issue type of an issue?

I don't think this is going to be a "random" order, I think you'll find it's alphabetic. And I'd guess your Aha rank data is probably not intended to be seen as alpha.

Remove the resolution field from the "create issue" screen. (And "edit" if you've got it on there as well). Resolution should only ever be used on a transition screen.

An "orphan" account would be one that has no administrators at the top level. Atlassian Cloud won't let you do this - you can delete any admins you want to (including yourself, which will then, of course, lock you out), but you can never remove all of them - the last one you try to delete/remove will be blocked from…

You'll need to log in as one of the other admins who have the power to admin accounts and re-enable the one you've disabled.

The only size quota Confluence imposes is a maximum size of attachment, and that's a global setting.

How are you creating the issues? Are people typing them in, or is it via email or a combination of both? (I'd ask about automations normally, but you said you've not got any)

Because it needs an email address for you to send email to. I think I am missing something in your question here though. Could you explain in more detail? "When setting up a custom email" is probably where I am stuck - what are you doing there?

A select list would probably be the best option - single value in the field, with a controlled countable list.

This is what it says - "error reading from remote server" - the proxy has passed your POST command to Jira and Jira has not responded with anything that works. This could be a misconfigured proxy, or that Jira is not configured correctly, or that the POST is not a valid thing to send on that url, or Jira isn't responding…

Permissions are done at a project level, not issue type. You can do it with a bit of code, although it is quite blunt. If you set up an "issue type security scheme", you can use post-functions to set a security level differently according to whether it's a bug or support request (either by writing code that checks the…

This is almost exactly what I do. I moved to scripts on disk very early on so I could store them in source control (that was before we had Bitbucket, but that's where I store them now) I sometimes use a fourth (complex) naming convention which includes an indicator of the purpose of the script and/or the project it was…

Ok, you flagged it as Cloud, so I had to go with that at first. But it's Server. You have chosen to download the .tar.gz version which is the recommended one for OSX as selected in the download screen. You can make that work on windows, but you'll need to find a file utility that can decompress and expand the files within…

It will not interfere with anything people are doing, although you might note it loading the resourcing a bit more than normal running. I think I've only seen it have a noticable impact on the performance once, in a large instance (1/4 million issues, unlimited users), but even then it wasn't painful for the other users.

This can happen if indexing or a transition have a glitch. The problem makes the workflow data not match the issue data and Jira can't work out what any conditions are for it so it hides all transitions. Try going to Admin -> Integrity checker and run the checks related to workflow and status. If this is the problem you're…

Rearrange the imports up to the top. Remove the line "return completedSP", and change the last line so it divides by completedSP