Nic Brough -Adaptavist- Expert

Set up your DNS so that your server can be found on your domain where you want it, then change the base url on the Jira server so that it uses the domain server name instead of the ip address.

This is too vague a question to answer. High availability of what? Are you on Jira data center? Version of what? Version of what is suitable for data center?

My guess would be because the issues were not flagged as "done" when you ended the previous sprint. "Done" on a scrum board is the last column on the board, not just a done status or a filled resolution.

People who can see the request can see the comments intended for the customers People who can see the issue can see the comments intended for "internal" people (and the comments intended for the customers)

Not from the field names I'm afraid. System fields have names rather than customfield_##### but a lot of apps and applications add custom fields then treat them as system fields. Field ids are not consistent across cloud or server. You can't supress them from the editmeta if they are enterable, no. that's the point of it -…

The short answer is that "current" means "what people land on when they ask for a page now". Not-current means "every revision of everything older". Simple example - if you had a really basic Confluence that only served up one single page of content, then your "current content" would be 1. If that page were on version 87,…

Cloud gives you no access to re-indexing, it does it when it needs to, which is infrequent and usually only when you change fields in ways that force it (changing a searcher for example). That actually applies to Server too - "often" should be months apart or when you make changes that need an index rebuild (again,…

These are all "system" fields, ones that are sort of background (and injected by Jira Software) The Development field is not really a field, it's a way to display a load of data from linked development systems. Technically, there's nothing in it really, it's a panel display. {} simply means "nothing there" The flagged…

You'll need to add "won't do" to the workflow. Might not be the best option - most of us would consider "won't do" (or in this case, "duplicate") as a resolution saying why we consider the issue "done", rather than a status, but if you need it as a status for reporting, that's fine. Ask your admins to add it to your…

No, that can't be hidden yet (Personally, I'd guess most people don't want it hidden, it's probably in the top three things we have to ask of questioners here and hiding it would be a monumental pain for us and them)

Pretty much - it's not for changing config, it's for working with issues.

Automation updates data on existing issues. It's not for doing defaults or templated prepopulation-leading-to-reams-of-junk-data type things. If you want to stick a standard label on an issue as it is created, yes, that's what automation does. After a human commits to creating the issue. (But I'd warn you that sticking the…

Ok, that's the workflow section, not really status, it's listing the transitions out of the current status into others. There are three reasons it might vanish * An admin removed your permission to transition by amending the workflow * An admin removed your permission to transition by messing with the permission scheme or…

Ok, you have to remember that this community is mostly here to talk about Atlassian because we use one or more Atlassian systems. Most of us don't know what Altair might be (my first thought is one of the brightest stars in our sky). But we can get you a bit further - you'll need to sign up for an accoun, ask the admins of…

Hard to say - you've told us "my account doesn't have access", but that could be paraphrasing all sorts of different error messages. Could you tell us what you have clicked on (not the exact link, just a description of what in Confluence you've hit and what sort of page you are on - the attachments for a page for example,…

What do you mean by "issue status disappearing" and "issue status were missed"? Did a load of issues spontaneously change to a different status with no warning and nothing in their history? Or did they just drop off a board but retained the same status? Or were you unable to search for "status = <something>"? Or something…

No, I think it was me not quite grasping it, your description was good, and your patient explanation of it for me was excellent. But yes, everything is pointing towards some problem with your index. There's absolutely nothing wrong with your voting, there's something wrong with your Jira that your voting system is exposing…

Ah, translation is always "fun", especially when we're in a field that has its own jargon. Your answers and screenshots are perfect, solve all the translation problems I was having. Resolution is a "fun" field, but to start off simply - Status is an indicator of where an issue in its process flow. Jira mostly uses…

Neither of those are actually problems! Someone with the Confluence Admin right can always see all spaces headers. Not necessarily see the spaces content or existance when they're wandering around Confluence content, but the headers (where the admin happens) is always accessible to admins. Imagine Dave is an ordinary user,…

No, the workflow view does not hide transitions just because the current user might not be able to see them. It would be a massive pain, and a lie, to do it anyway. Think through these scenarios: User thinks "I want to reopen an issue". No option to do it, can't see a transition for it on the diagram, they have to bother…

Ok, the vote being a single field doesn't really make much sense in terms of it being a vote (it's just a flag field), but it does contribute to the "this is a really simple action", and tells me it is just a symptom, not the cause of your problems. A single change, to an issue, such as setting your voting field, should be…

Jira doesn't have "masks" and "layouts" refers to how cards are structured on boards, not issue views. I am therefore very uncertain about what you are really talking about when you use those words. I also think they're confusing you as to what you are really seeing. You also talk about a "solution" field, while referring…

Rather than use us as a search engine, could you try reading the Atlassian documentation? Pages like https://support.atlassian.com/jira-software-cloud/docs/organize-work-with-components/ exist to answer questions like this, and they're easily findable with search engines.

Run a search for "particpant = currentUser()", save it and use it in reports and dashboard gadgets

Do you have view and edit rights on the issue you are trying to link to?

Ok, that's good (not looking at the database). The change here happens because AO does not have code for storing times or dates. It just stores a date-time. Those need dates on them, so if you are writing code to use just the time part of the data, your code will need to cope with the date part. (Note that for date only…

That sounds like you are creating a team project in someone else's Jira or Trello. Sign up for your own Jira or Trello workspace and create the new stuff in there, it doesn't have to have anything to do with the other person's systems.

Ok, there's a couple of things that worry me here, but I need to ask some more questions, with a little bit of context to them. Jira's search engine relies on a physical index system on the disk - it's a copy of most of the data in the database, but organised for searching (Jira's database is not, it's, at best, just a…

You don't need to delete anything to start a new project, I am a little confused as to why you think that. If you're using (free) Jira Cloud for your existing project, and you are not the owner of that Jira (and you say you've lost contact with the owner), there's nothing to stop you starting your own free Jira Cloud…

There is nothing to fix. As described above, if you wish to stop hearing from a project, ask the project admin to remove you. If you no longer have a use for a system, ask the system admins to remove you from it. Remember that your presence in someone else's system belongs to them, not you.