Nic Brough -Adaptavist- Expert

Jira makes all the fields available to other applications, as seen in the UI. So I suspect your problem is with "Front", it's that not showing all the fields, not Jira.

The subscription is by service, not person. You'll need to subscribe everyone, or get a second Trello for your advanced user and use separate boards.

> Why cant you give me your contact details somehow? I'm a volunteer here, like the rest of the community. We don't give out contact details in public because that just means spam, plus vast amounts of people asking for help for free, which we don't have time for! You're not going to assign anything to me, or the others,…

What do you mean by "lists" and "moving"?

Yes, the app is not showing you a field that you have set required, so you can't create the issue. You'll either need to make the field optional, or configure the app to show you the custom fields (I'm not familiar with it, I don't know if that is a code change that the authors would have to do)

Yes, that's correct. When someone who has reported an issue is inactive, they appear in the history and the reporter field, but you can not select them as a reporter of a new or edited issue.

When you say you are trying to rank sub-tasks, are you talking about the order of sub-tasks within their parent issue, or outside their parent (in the backlog, issue navigator or reports?)

If you just disable them, nothing will change in Jira (except that they can no longer be selected in the fields). Exisiting data will not be removed or changed. People will not be removed as a reporter unless you explicitly change it to someone else, or completely delete the user.

Jira 5 did not really have project types. You can still create projects that you can then use Kanban boards with (assuming you have Jira Agile, which is what Jira Software was called for that version of Jira), but there's no project types etc. Hopefully, that answers the basic question, but it does lead to some questions…

Correct, if you delete the field (the header information saying "this field is here"), then the issue data has nowhere to exist, and hence simply gets deleted.

Possible, yes, but you do need to be careful about where you do it. You can get the values for a scripted field in the same way you get a value for any other field. But. The easiest way to explain this is to say that "scripted field values are built when an issue is indexed". This is not the truth. But it is an…

This appears to be normal, it looks like you have started a Jira and then started another one of the same instance (install). It won't run because it already is. Try shutting down all your Jira services on this machine, and only running a single one.

Yes, but you'll need to do a full export and then import only the project you want, there's no "export project" really.

There is an open issue for priority schemes to come to Cloud, but it does not appear to be moving.

Apologies for the delay in replying - had this open on a computer that I didn't take with me to my family emergency, and only just opened it up again! Let's concentrate on a single place, let's forget view/edit for now. Have you set up the below? (I'm using example text for names and content, obviously replace it with what…

No, we know nothing about your systems, we're a community of people here to talk Atlassian. Your best bet is to ask the people around you, maybe the ones who asked you to use Jira, or the one who got you your account.

They do not, you'll need to have the admins publish the list somewhere, or rely on "get help" emails going out to them if that is enabled.

It's not possible, Confluence has no support for pop-ups.

Confluence does not care what the storage for the attachments is, it can be any file system that a java process can read and write. It does need to appear to be local to the server, but with things like NFS, you just mount them directly into the local file system so they look local. (It does care for the index and working…

Stop reading the database, it's the worst possible way to look at Jira data.

There is no change, you need to move things into the last column so that you can accuratly represent "done"

We cannot, we are not your admins. Please ask your administrators.

I have been grumpy there, but it is purely because the previously accurate answers have been ignored. I suggest that this still seems to be being the case.

I am going to cheat a lot here. I have four. * I went to Kew Gardens for an ACE and met an Adaptavist for the first time (I'd worked with them before, but never physically met one), plus an Atlassian, and then a load of other people in the ecosystem. * I went to an ACE and met Bee. * I went to my first Atlassian summit, as…

I know that was terse, and very grumpy, but it is still right. It is grumpy because I am so very tired of explaining it so so so many times. Subtasks have no place in a backlog, because they are not items you commit to doing outside of their parent story. Your teams are doing everything right, but you need to forget…

A deleted issue in Jira is totally gone, there's nothing left, so "we would like to open and read for audit" is not going to happen if you choose to delete. (There's nothing wrong with the idea of retention for audit, I just want to be 100% clear that "delete means delete", which breaks your audit automatically) You will…

I would guess your "obsolete" or "done" issues are not mapped into the right-hand column on the board.

No, there's no real "work around". It's evolved this way because almost every organisation tends to have a consistent working day/week pattern

Could you explain more about what you are trying to achieve? You don't need Atlassian's approvals for accounts, and it is unclear what you mean by "Crowd1 KYC"

You will need to talk to your admin about the lock-down, there's not a lot else we can do!