Nic Brough -Adaptavist- Expert

No, if someone can read a page, then there are always ways to copy it. You could try some javascript that asks the browser not to allow copy, but the browser is free to ignore it, and that sort of thing is very easy to bypass. If nothing else, fetch the page content over REST.

Well, you could hide the search box, and even get rid of the search UI by turning it off. But there's not a lot of point, as you'll still be using two differing indices.

The "logged users" here by definition cannot be allowed to watch, vote or look at issues - you have not licenced them, so they can't be let in.

Well, you could put another one alongside it and then hide it the old one. But that's trivial. The ripping out is looking and changing all the places Confluence uses Lucene. Unless you really wanted to be using two separate index systems, one for search and one for reporting, macros, page relations and and and. If you…

Where are you "going to database version"?

You've mostly got this right, but there is a problem. You're serving up * Jira <domain>/ * Jira Service Desk <domain>/servicedesk * Confluence <domain>/confluence The first one is the problem - it's serving Jira on / which means everything under / is expected to come from that Jira. You won't be able to ask for…

Not in the UI. You can build urls like the ones you are suggesting outside Jira, but there's no variable substitution inside it. Jira stops listing issues at 1,000 to prevent performance issues (but that's just the listing, the data is all in the results) Could you explain what you are trying to achieve here? We can…

Field Security from Quisapps works well for most people.

Sorry, it's not part of the summary, it's the epic colour. But the rest of my answer is right - it is not a Jira icon and you can change it by clicking edit. And the issue type is not story, it is an Epic You can't change the default colour.

They're doing this for Chinese users because Cloud is not usable in China.

It is not from Bitbucket. When Bitbucket has a misconfigured integration, it names the third party service or app that is not working. Bitbucket might give you something like the error message you are seeing but the line before or after it would say what app or remote service is failing the connection. You need to ask…

What "export" are you using?

Ohh, I think there are two of them in our "random gadgets we've stopped using" box. Not my thing (I bimbled along with a nokia 3310 until smartphones arrived), but Chrissy loved both iterations she had, and they were at the top of my list if I lost or broke the nokia. My only complaints about them were that: * the spring…

For me, the smartphone is good and bad. It's traded "having an internet-enabled computer in your pocket" for "having to worry about charging the bloody thing all the time". Excellent multi-tool, but annoying to have to charge it daily instead of weekly. Must admit though, I had to dump my first one because it wasn't…

If you did a bit of digging, you would indeed find that the numbers are immutable database entries. You can change the name of something but not change the unique id for it. I'd recommend not bothering to do that digging, it's exactly what @Hana Kučerová has said

Yes, if you want to do it that way, you will need to create a new service for every project. Hint: don't. Get people to talk to each other and work together in one place. It's faster, cheaper and better to share than to silo.

Can't say I have a "favourite", to me, a 'phone is a tool for making calls and short messages (literally SMS). So as long as it does the basics, I don't really form any feelings about it. I've had a mobile since the late 90s and been through a few, none of them being particularly memorable. I remember watching "The Matrix"…

There's not a lot we can do for you here. It sounds like you are simply putting the wrong credentials in on the different devices.

You'll need to ask this of Micro Focus Fortify, not Atlassian - Atlassian didn't write what is giving you the error message.

"we need to assign more than one assignee for a ticket" No, you do not. That statement is wrong. By all means, add something that says "other people to talk to about this issue" - a group picker, a multi-user field, even a label. But you should only ever have a single human assignee.

This cannot be done. The issue key is always <project>-<sequence>. The issue type is irrelevant.

You've answered your own question - it's asking for admin rights because you're trying to do something that needs admin rights. Could you explain what you expect it to do differently?

Most of that wall of text makes no sense to me. The one bit that does make sense right is that you want to have a 1:1 relationship between a Jira issue's status and your external system's item's status. The mapping between Jira-Status and External-Status should be 1:1 and I really cannot discern why you are looking at…

Often known as "sharepoint for cloud, where documents go to die in a cloud rather than on a sharepoint server".

It will only be burned down during the sprint when it is in the "done" column, if you move it out, it is re-opened and hence not burned down on any more. After the sprint has ended though, changing its status will not affect the burndown on that sprint. Jira has moved on to a new sprint.

Er, that's this post...

Always worth asking!

You will need to use the custom field context calls, as documented in the link I gave, to get the context for the custom field you are querying the contents of.

There's no way to do this. If you were on Server, you could do some stuff on the networking side - stick Jira and Confluence behind a proxy, with which you could then code some stuff that tried to do browser or device identification before letting the connection through (that would stop casual users doing it, but not…

Thanks for the explanation, but it raises more questions and suggests more problems than I expected. The core of this is probably "use the transitions properties to map Jira status with the status of the external system" This makes no sense to me. A transition in Jira is not a status. It is a link between steps (status) in…