Nic Brough -Adaptavist- Expert

If you want to make any use of a dummy (like naming it in fields like assignee), you will need to licence the "user" as though they are a real person.

Yes, you can do this, you'll need to create a new account in whatever your directory system is (Atlassian Access, Google account, or a dummy Atlassian account) and add it to your Jira in the relevant projects. This will take up a licence though.

Welcome to the Community! It sounds like your workflow does not have a transition that goes from the status your issue is in, back to a status that is in the assigned column. Or, if it does, then there is a condition on it that stops you using it. Most Jira systems are set up to allow non-admin users see the workflow…

Welcome to the Community! Jira is an issue tracker, designed with a strong lean towards open sharing of tracking data. It is not a messaging system, certainly not a private one - the whole point is that you share your issue information. So, you might be able to find an app that enables some form of private messaging from…

Welcome to the Atlassian Community! Please could you explain what this has to do with Atlassian software, and give us a bit more context as to what you are trying to do? Добро пожаловать в сообщество Atlassian! Не могли бы вы объяснить, какое это имеет отношение к программному обеспечению Atlassian, и дать нам немного…

Is the script editor showing you any warnings or errors? Do you get what you expect in the logs from the log.error line? Could you change the last bits of the "set assignee" code at the bottom, changing the "set assignee" line so it goes into a variable and we can echo that out in the log to check it actually has got a…

Message fields for (view and edit) come from the Jira toolkit app. They do not hold any data on issues though, they just put text on a screen when they are added to them. Like other fields, they won't appear on view unless they have data to show, but unlike other custom fields, also hide themselves completely on edit…

Yes, but you do not want to do it. The issue type id is used in several places, and unless you have a 100% complete list of all the places it might be used and a thorough understanding of the database, you are probably going to break it. Why do you think you need to do this? What's wrong with accepting that your migration…

You could use the REST API to get the details of an issue (it'll need to be anonymously accessible, or you'll need to have a token for your script/application to do the read with)

I'm not sure I understand what the question is here. To use the correct version of the database, use the correct version of the database. In this case, the connection to the database was set up to point at the wrong database, which was running an older version.

You can do this, because there's a trick in understanding what "done" actually is - there are two possible meanings for it. In most cases, people will try to keep the meanings the same, so they don't have to think too much about it. The difference here is that * "Done" is usually a status that humans use to say "we are…

Scriptrunner is never going to have an entire JQL engine written into it to replicate what a JQL search already does. The simple thing to do here is run the JQL and work with the results. A search will return a pile of issues, and you can then look through the results to see if the issue or issues you are interested in are…

There's a peculiarity under the hood here. Bitbucket Server and Bitbucket Data Center are the same software, and a DC node installation is exactly the same as a Server installation (it's not quite the same when you're adding more nodes, there's a bit of extra config to do). It's just your licence that makes the first node…

I don't know what you expect us to do about this. You need to talk to the adminstrators of the site you are trying to join.

That's correct, the sprint completion date is noted and stored when you end the sprint. There is no reason to change it, as all that will do is destroy your historic reporting.

It won't tell you much. The default status are things like: Stat Status Meaning OpenOpen To-doTo do In progress In progress ResolvedResolved (issue has a resolution set) ClosedClosed (same as done)

There are a load of scripts that show you how to work with custom fields in the Library. Have a look at https://library.adaptavist.com/search?page=1&products=jira&term=custom%20field for one that is close to what you want to do.

Welcome to the Community! You will need to do some coding to create new things like that. Start with a look at Forge - https://developer.atlassian.com/platform/forge/

There's a problem with the network or browser that is throwing an error. Without knowing what the error is, we can't tell you any more than that. What is the actual error?

You can show the ranking field on a screen, by adding it to the screen, but it won't be of much use to you. The data in it is intended for comparison with the values on other issues and isn't human friendly. This begs the question of why you want to see the rank? What would it help your people with?

That error message does mean what it says - the account associated with that email address has not been granted access to Jira. You will need to get your administrators to explain why, and fix it. Essa mensagem de erro significa o que diz - a conta associada a esse endereço de e-mail não recebeu acesso ao Jira. Você…

On the sprint.

No, it isn't. It's just different to DC. It's different software, run differently and therefore has different admin options.

Fields do not get used by workflows directly, so I'm not sure what you mean by "removed the customer field from the workflow" A field's mandatory flag is a function in the "field configuration" for the issue type in the project. I suspect what you have done is removed a field from the create screen, so when you create an…

Nope, not a bug, please re-read the previous comments.

We can't tell you what your process is. You will need to ask the team who built the workflows what they mean by their name for each status they have created. "Done" is the only one in there that is a standard off-the-shelf status, and it means what it says - a "done" issue is done. 

Welcome to the Community! The status is descriptive of where an issue is in the life-cycle your team is in. We can't tell you what your status mean to your organisation. Jira does ship with a number of status, but the three you have named are not off-the-shelf ones, they've been defined by your admins for your teams, based…

I think you may need to talk to the administrators of the site you have been invited to join.

Welcome to the Community! I think I'm a bit stuck on the detail of your question. You say "an easy way to view the ticket history" and the answer to that is "click on issue history for a list of (almost) every change to the issue" Next, there is "is by going to "Your Work" then viewing recent entries" - that's a separate…

You can't do this, and I think you've already worked out why! Not because the idea or the code are wrong, but because text fields cannot be searched like that. They take only fuzzy searches, and depending on your choice of project keys, the JQL "Issues linked by realises" ~ XYZ-1 may not reliably do what you want! The…