Nic Brough -Adaptavist- Expert

It was available natively in Jira 7.0 and all later releases.

Jira is not a free-form editor where you might usefully sprinkle your text with labels and other meta-data. Each field has a purpose, and fields are more powerful than free-form text because they have a purpose. To label an issue, use the label field.

What do you mean by "same sequence of data entered in old tickets increment counter, time spent"? That does not tell us what you might be looking at in Jira.

Your screen scheme is probably using the same screen for create and edit. Split that into two separate screens, with the create screen having the field and the edit screen not.

How are you representing your "features" in Jira?

No, it's an online service, not a distributable server product.

Remove it from the "edit" screen for the project/issue-type

Your admins have put a validator or post-function on the transition you are using and it is broken. You'll need them to fix or remove it.

OK, so you'll need to talk to your admins about what they have done to break it.

It sounds like you are not mapping the issue type when you are defining what fields to bring in, and Jira is simply going back to the project's default type.

You need to talk to your Jira admins - they will need to either make the field optional or put it on the create screen so that you can fill it in.

I think we need to see your board to help you with this. Jira's "last column" thing is very blunt and simple, and should not be doing what you are seeing.

This warning is telling you that your server has been modified away from what Atlassian distribute and support It is not an error, it is just trying to tell you that the changes you have made on the server could be destroyed by the upgrade, so you might want to look at why you made them and think about re-doing them if you…

I would look to fix whatever you've done wrong in the install, or forget it and just move to your inferior alternative.

The burndown is worked out on the basis of what issues are done and what is not. An issue is done when it is in the last (rightmost) column on the board. I suspect your burndown is actually correct if you look at the board columns.

From what I have seen before, Cpanel does not have the flexibility to support standard web-application installs. To simplify down to the basics - can you get to a command-line that enables you to run the installers for Jira, Confluence and Bitbucket?

In reality, what you think you want to do is nonsense. So don't do it. Do what works instead.

Cynical about my users - no, I talk to them. But it is very very important that we understand the words: A cynic is what an idealist calls a realist.

You would need to write an app that can make these changes. For simple stuff, I would not bother, but if you really do need complex forms, then @Kate Caldecott has the right answer. I don't use Proforma a lot myself, but when you get to a point where you start to think about it, just stop and go with what Kate says,…

No. Ok, yes, there's a schema available to look at. But you really really really do not want to use SQL on a Jira database. Frankly, the database is a bloody mess, do not waste your time with this. Last week, I got paid for 12 hours work building an SQL query for a client who insisted on doing it with SQL. I got them a…

Actually, no, an issue can be in more than one sprint. I'd agree that in an ideal world, it absolutely should not be. Because that tells us that people really have no idea what they're doing and need to have a long hard think about their utterly broken processes. But, technically, it could be in one, two or many sprints.

No, you can only assign to active users. This does make a lot of sense - if someone is inactive, they're not going to do anything about the issue because you've deliberately said they're not relevant to your organisation any more. But your situation does make sense and I can see exactly why you're asking. There's…

Because it's wrong. As you have had explained above and ignored.

JQL finds issues, not boards (or projects, workflows, users, etc). An issue can appear on many boards too, so I'm not sure quite what you are looking for here, especially as you've already named openSprint() as the function you probably want.

Confluence does not record who changes spaces.

Not in Jira, it does not record searches. But if you are using Service Desk with Confluence as the knowledge base, Service Desk does record what articles people land on when they're looking for something. If you go to the Jira Service Desk project linked to a knowledge base and find "reports", the "requests deflected" and…

If the two issue types are configured the same, and the issue type is on the "edit" screen, then you can just edit the issue type. I'd guess this is not the case though. To change the issue type when they are configured differently, you will need to use the "move issue" option. It will ask you for a target project and…

You already mentioned populating externalid on the Jira issue - I'm not sure that's the right place, as you say it was removed (I think it's limited to being written when importing). But it's a good approach - create a new custom field to store the reference your application sends over. Then, when your application wants to…

You don't. Customers should not be assigning teams.

You don't. The right-most column on the board is done, that's it.