Nic Brough -Adaptavist- Expert

See https://confluence.atlassian.com/adminjiraserver/installing-jira-applications-on-windows-938846835.html

It upsets me because a) the request is "make things broken for people". b) most of the responses are from people who have not bothered to read what has been said previously. Please, stop doing point 2. Go read. Go understand, think about your users, all of them, not just the 75% who won't have a problem with you doing…

>Why do you have this idea in your head that nobody wants this Because they don't. It is utterly irrelevant that "hundreds of people on this page" want this when it is something that is a bad idea. In those terms, I live in a counry that thinks socio-economic suicide is a good idea. Just because asome pople think it's a…

Yes, very much so. The limitations on a trial Atlassian system are really just "out of time". There is no difference in functionality or how it workds, it's just "trial = ends at some point" If you like what you have now, just go for it, the default behaviour is actually "these people have used it for a trial, they chose…

iframes tend not to work with Jira because it has a lot of stuff that isn't iframe friendly. There's no plan to change that because html 5 pretty much dumps ifranes totally. I think there is a good question here, but I can't see what it is because of the legacy tech question. Could you tell us what you are trying to do?…

Could you explain what you mean by "provision to our users"? I am also curious about "BitBucket is also not capable yet "? Both of these systems have een available for years and I am not understading what you are expecting of them?

Some versions are "officially" supported, but a much wider range works fine. I regularly use Jira and other Atlassian stuff on unsupported browsers and it's fine, but, that said, I tend to stay well away from the non-standard and awfulness of IE based browsers. That might change when MS finally admit that they can't…

There are simply not a lot of exports from Confluence. It's a system that does not expect us to want to move to inferior ones and hence sees no reason to enable downgrades. Your export routes are word, pdf, xml or parsing a backup. None of these will work well for Sharepoint, mainly because it is bad at handling them.

I cannot tell you that, I do not know how your teams work, or how they estimate things, but I can get it down to a quite simple question. Scrum needs to work with numbers. Humans see a lot of numbers in a lot of different ways but Jira needs a definitive number. So you should look at the two basic options: * Number of…

Atlassian have no reason to create a route for people to leave their platform, and the community, while a bit more open-minded, probably don't either. I cannot speak for anyone else in the community, but I can tell you that I have no idea of what might be suitable for importing into Sharepoint, because I acquired a…

Not that we have logged, yet (that I can find, but please bear in mind I'm not in support or product, so there's a lot of stuff I miss). I'd ask for more information on "facing issues... with the Team field" - what is going wrong for you? Could you describe a failing in detail? Not all of them, just one for a starter I'd…

You can just put file://<path> in as the url for a link. It does require the browser to understand it though, and "file" is not a standard so a lot don't.

You don't. The technical version of the answer is that there is no blank page template. There's nothing to template, it's offering you two fields with no prefilled data at all. For Server/DC Confluence, there are a couple of tricks you can play where you effectively stop "create empty" from being offered to the end user…

Removing the field from the screen will stop more issues becoming fixed on edit. As for the create screen, no, you absolutely do not want the resolution on the create screen. Unless you really do want to always create issues that are closed and need no more attention?

When an issue goes into a sprint, the sprint gets named on the issue, and it remains there when issues go into the next sprint, so you could write: sprint = "sprint 12" and sprint = "sprint 13"

Business projects don't have swimlanes, so I assume you mean "columns". The answer is no - the columns in business boards follow the workflow.

Run a search for the issues you want to remind them about, save it as a filter and then use "subscribe"

>When the approval sub-task is created it isn't assigned by automation, it is assigned manually by a user Ok, that might explain it - if an issue is not assigned, it can't be in anyone's "assigned to me" list. The issues will appear after they have been assigned to people.

With simplified workflows, the workflow follows the board changes - each column is a step in the workflow.

You fix this by breaking up the work into teams, who will run off boards containing only issues appropriate for them. When you run into this error, the problem is not that there are too many issues, but that you have a process that puts everything in one great big pile instead of splitting it up into things to be handled…

Server/DC and Cloud are now totally different products, just ones that have a data-set mostly in common.

The evaluation databases (hsql or h2, depending on version) are not supported and never have been. Moving to Postgres or MySQL is a very very good plan. I know you didn't ask, but I'd recommend Postgres over MySQL, mainly because Atlassian code for it first and run most of their stuff on it (so it accidentally gets more…

Not directly by the user. The problem is that you'd have to create the issues as a batch. The sub-tasks cannot (and should not) exist without a parent, but you don't have a parent until you've finished creating the parent, so you can't create them during the parent create. You would have to do this as a batch process -…

This is rather an interesting one. The search for "assigned to me" and "my open issues" are very simple and really do look just at the assignee. It sounds like the issues are not being indexed as they are created. But my problem there is that Automation and other scripting tools that can create issues, especially the big…

Yep, that's the expected behaviour. You need to remove the resolution field from the edit screen - it is not supposed to be used there.

For most Jira systems, I would change the permissions in the project, setting them such that the agents can see all the issues and be assigned to them (and possibly do some other stuff like letting them assign, so they can self-allocate issues from the queue , log work etc), but then only allow the "assignee" to edit or…

Epics need the epic name field to be filled. Stop using epics in business projects, you clearly don't need the functions they provide.

I think you need to head for a support issue - it looks like the app cannot handle whatever authentication your ms-sql is doing (while I suspect you've got other tools that can)

We can't really start to debug this without knowing * The JQL query * How it is being posted (the lines of code or command that is posting and the language it's in if it is not obviously a shell script or easy to read) * An example of an issue that is duplicated in the response

Well, it can restrict access, but the other four are good reasons people go to Server/DC from Cloud.