Nic Brough -Adaptavist- Expert

With the translations, technically, yes, that's exactly what you do - if you select say German, as an alternate language, then the field name will come out in whatever is in the language pack for German. So if you could find or create a language pack for "my English where we call versions releases", you could use that, and…

What is your base url set to? I ask because accessing a Jira on anything other than its base url can do this sort of thing. If the problem you have is that, then you should see your base url has been set to localhost:8090/jira rather than mycompany/jira

You can translate them by using a different language in your profile, but you cannot rename them. What is your reason for wanting to rename the field? It's not intended to be a release field (although releases are a sub-set of your versions), so I'm not sure what you are looking for.

Welcome to the community Daniel! Yes, there is a standard port, it's 443. That's the standard port for SSL, and almost all software assumes when you say "https" and do not specify a port, 443 is implied. I don't think the port is a problem in your command. What is the error message you are getting?

There is not a lot much to expand on here. The last line of the error you have here really is telling us the core of the problem - the user sending the mail does not have permission to send mail. This will almost always be down to a misconfigured mail server, a sender that looks malicious, or one that is configured to be…

If you want to lock it down this much, then you can. As an administrator, remove all the issue types other than Epic, Task and Sub-task, define a single set of schemes for projects and only add the custom fields you need, with a global context. When you create a new project 1) Do not select "next gen" projects 2) Use…

There's two "Edit issue" is needed if your source and target issue types have identical configuration "Move issue" is needed if they are not

A standard 25+ user server licence comes with a "developer" licence which you can use for test sites.

Core does matter, but the software licence includes the core access your Software users need. Try going to Admin -> Manage applications (not apps) and you should find Core, Software and Service Desk listed, with a box for entering licences. Go to edit the Core licence and simply blank out the key. That should make it…

Sometimes it is. Try clicking on "log work" and look at the two enterable fields you get - "time spent" and "time remaining".

No. "total work time is 4h and logged time is 1h 30m so remaining time must be 2h 30m" is a false statement. It is true in the case where no-one has changed the remaining estimate. But in this case, they have. What I said was nothing about the calculation, I said that someone changed the remaining time. I'll try to phrase…

Business boards are not configurable like Software boards, they don't have layout options.

You should do this with conditions in the workflow. See https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/

Associating the issue type screen scheme with the project I think

No, it is literally those that people have chosen to share it with.

In classic projects, yes. You will have to have all the possible resolutions in the global resolution list, but you can then use workflow properties to limit the list offered to people when they resolve an issue.

Many times. I think that's part of what made me turn to consultancy - asking people why they want such a strange or torturous thing to be done, and why they don't want to do it the easy way.

There isn't one. A report like that is of little use to the humans - what would you actually do if someone gave you a list of 400,000 items? Even if grouped by space (which you can do by looking at space tools -> content, for each space), you could still have thousands of pages to think about. And that's before you look at…

Could you explain what this has to do with Jira?

Varied I never know what the next question / request / fault is going to be.

Sorry, I meant to go back and edit that comment as I missed the last sentence I wanted to add, which was along the lines of But they are expandable if you click on them Glad you found that for yourself :-)

The "off the shelf" way to do this is to make sure your workflow sets and clears resolutions correctly and then re-open and close them all. But I find that ugly. I prefer to * wait until no-one else is going to be using the project(s) affected * go into the project(s) and add the resolution field to the "edit" screen they…

If you have not changed anything on the Celoxis side, then my best guess is that the SSL certificate that Celoxis is using has expired, and you'll need to install a new one.

Yeah, that's why I throw them through log analysers to be honest.

It takes it from the list of people that the issue has been shared with - usually a close match to the "participants" on the request.

Ah, the text of the labels, ok. I'm afraid the text of labels does not show on the cards, they would take up a lot of space on a card Atlassian prefer to give over to other fields.

Ah. No, there's no way to limit the selection of which sub-tasks are offered. If they're available to the project, they're available to all types of issue in the project.

When you log work, you're usually entering a duration, not a time. Durations are not represented in a 12 or 24h format, they're a number of days/hours/minutes So I'm a bit stuck on where you're entering this log - is it a start and end date/time pair somewhere?

Use 60d and 90d in the same way.

I think you mean "relative", which is not the same as subjective.