Nic Brough -Adaptavist- Expert

No, there's no way to turn this off. Sub-tasks are always considered to be part of their parent issue, it would not make sense to have a version different to that of the parent.

For a classic project, you can put the ready-to-deploy status in the done column on the board. For a next-gen project, there's nothing you can do, you just need to have the last column contain a done status and maybe track "ready to deploy" with a field.

No, that doesn't work, as explained in the previous answers. Please have a re-read of those.

So how are you exposing your local Jira to the internet? What port forwarding or proxying have you set up?

* Anchors is the old macro, now you do it with this: https://support.atlassian.com/confluence-cloud/docs/insert-the-anchor-macro/ - note that it's a bit of a pain if you want to jump within a page, you have to get the headers right and saved before you can generate the link automatically, then re-edit the page to add it…

Confluence has templates, you can create new ones for a particular space in the space tools or create global ones from the global admin section. There's no import function for templates, but copy and paste from a word doc should at least get the basic stuff into a template

The portals only support field types that Service Desk is aware of, which means fields that are of the built-in types or extended from those types. Power custom fields are neither of those, Service Desk can't know how to handle them.

You cannot use the numeric IP because that's only available inside your network, behind your NAT as far as the internet is concerned. The migration assistant needs to be able to read it. You'll need to do some proxying and port-forwarding, based on the external ip address of your network.

It is possible with Scriptrunner on a Server install of Jira. Apology/Disclaimer: I work for Adaptavist, so, of course, it's part of my job to sell Scriptrunner. There may be other tools that can do this in the marketplace, but I do not know if there are. Because I've got SR "on tap", I have not needed to look. I do know…

I would start with a look at the application logs - what does <jira home>/logs/atlassian-jira.log say when you try to send a test email?

Unless you know what the problem is, there is no way to know where an upgrade might land on the scale of "make it a lot worse -> fixes this and makes loads of other stuff better"

In the project's permission scheme.

Yes, I would just grant them "browse project". That lets them see the issue without opening anything else up to them.

Not permissions, just the connection. I'm glad to say Cloud does not allow any direct access to the database behind Jira. You'll have to do whatever you're trying to do with sane methods of access - UI or the REST API

Ah, sorry, I should have expanded on that. Yes, participants are a request-level thing. But you can also have a field of type "participants" for issues - it is read-only though, it's not an editable field, it simply lists uses that have commented, or are the reporter or assignee on the issue (jira users only, not customers)

If you can't see something, there's no reason to link to it, you're just putting in dead links. So, no, there's no (logical, let alone technical) way to make a dead link into a live one without granting access to it.

No, the visibility options are for issues, there's nothing stopping people using a report. There's not a lot of point - if they can see the issues, they can work out the report from that anyway. And if you take the reporting away and they try to get something a report would tell them, you'll find they often get it wrong…

You don't. You will need to throw away all your reporting and move to proper methods to do it (SQL is the worst possible way to try to report on Jira, hence the "not proper"). This means using the reports or apps built on Cloud to do it. Atlassian have (yesterday) opened the floor for early access to the Data Lake though,…

Jira Data Centre, and Cloud, are both subscription models. You pay annually (cloud has monthly options too), and the software stops working at the end of the licence term. Server is a perpetual licence - you get a year, but if you do not pay maintenance, everything continues to work fine (with a nag message for…

I think, in theory, you could do this. Legally, I'm not qualified to go into it. So I'm not sure about "allowed". However, on a technical level, it doesn't matter. You can not send the credentials from Jira to another service, as Jira does not have them. There's nothing it can send. You need to be looking at shared…

Don't forget users can also be customers.

>Can I put the color to be seen on the card/story/task based on the status Yes, but it's mostly a waste of time because you already know the status from the column the issue is in. > Can I create a report from those created issues with their statuses that will be presented in swim lanes (customers) and which kind of a…

There is no way to make the system dashboard private. You never want to, as it's the landing point for users who have not chosen something else. Jira and system admins can amend what is on it. If you're worried about "leaking" information that you should not, then the system dashboard respects the permissions and…

No, as that defeats the purpose of the label field. Use a multi-select custom field instead, then you can completely control what people put in.

No, the picture you've given us is of a project with most of the features turned off. It's not done by user, it's project settings.

A very simple way to describe it is that "Users see issues, Customers see requests". Requests all have an issue behind them, as the main object that Jira works with, but customers have nothing to do with issues directly. They can't even see the issue, let alone be an assignee or reporter etc. There isn't a relationship…

No, the import is a simple "replace the data in the field" implementation, a flat "edit" action. You'd need to export the current data and concatenate your new data into the field before importing it back.

Yes, you have found the right answer, you need to increase the confluence user's file limits.

The error message says line 6 is failing. I think the code on that line is the one trying to get a date from the "start date" field. A null pointer error here means that there is no data in something you are passing into a method on that line. Either the field does not exist for this issue, or the data in it is not a date,…

You do not burn down on sub-tasks when you're doing Scrum, and hence Jira does not support it.