Nic Brough -Adaptavist- Expert

Not even a plugin can do this. The issue key is held in a numeric field for a start, so there's nowhere you could put a date string, and even if you could, all of the code that works with the issue key would have to be rewritten. I would question the "requirement" for this, I think your manager has come up with a really…

Yes, that's the page I linked to ("self managed")

You will need to pay for a 50 user licence. If you have 25 now, Atlassian will subtract the value of that from the cost of the new 50 licence, done by time (if, for example you've had 25 users for 4 months, they'll credit 8 months worth of your 25 user price) Pricing is at…

You can move the fields order by changing the "screen" they are on. But be aware that the main issue view screen re-arranges some fields, drawing them out into their own panels, so the order you put fields only affects the order within the "custom field" area.

Nginx is not "part of the package". A "by the book" installation does not include setting up a proxy server - it is mentioned as an option and you set up the proxy yourself. It's nothing to do with Jira, although a lot of us use them. The Jira I'm about to upgrade is "by the book" installed, but behind an Apache proxy the…

Some knowledge of java, and usually some html. But I would not bother doing it from scratch. Atlassian have Software Development Kit that provides a load of useful functions (At the most basic level, if I want to write a new Atlassian app for Server, I run "atlas-create-<jira/confluence/etc>-plugin", answer four questions,…

The plugin does not add fields, it provides the code behind them, adding field types to the custom fields. You have to add the fields yourself (this means you have more say over their configuration - you may only want them in some places, you might want different names and so on) If, for example, you have installed the…

You are misunderstanding the architecture here, and it's worth clarifying. It sounds like Jira was absolutely fine. Nginx is NOT Jira, it is a web-server. It is probably being used as a proxy to Jira in your case, so it's part of the networking route. The error message 521 was actually telling you "nginx is not giving me a…

You have used the "cloud" label for this question, but I think that's what you are asking and so these answers are for Cloud only, they do not apply to server or DC installs. * No. When you shut down the service, you lose all access to it on the end date, because you have said you don't want to use it. Atlassian will leave…

To change your url, you need to raise a support request with Atlassian, over at https://support.atlassian.com/contact - until recently, they did not do url changes, but they do now, as long as you don't ask frequently. Choose your new url carefully, while it can be changed, it is going to be with you for a while.

Oh, Oh, Oh, the first wristwatch was not intended to be a timepiece, it was a conversion of men's "pocket watches" for the more ornate women's clothing in the late 1890s or early 1900s. I have no idea who first did it, but I do seem to remember it was either an Austrian or Swiss person. (yes, I'm old, and I have several…

Is it a unique trait not to have one? I've got nothing I have not observed in other people. The closest I've got is people seem to think I'm a good asset in a pub quiz because I'm an information sponge in some fields. I've won quizzes based on * being able to yell "32,768" first when asked about powers of 2 (after…

Ahh, ok, I misunderstood, sorry. I think the problem is that Jira has no way of knowing that your clones of A and B should be linked, because each clone action is separate and done to a different issue. I think you can do this by writing a listener that catches that the clone of B has been made, looks back at B, works out…

What app are you using to provide test cases and steps?

The status field is already there. Look for the dark-blue rectangle just to the right of the middle, with light blue writing to the right of it. Attachment is not really a field, it will appear when the issue has any attachments (you need to have permission to attach files in the first place)

Sorry, I lost track of the thread. I'm afraid your screenshots are too low resolution for me to make out what is happening - the writing is just a bit too fuzzy.

You are absolutely right, I will always advise against it. It is so easy to get it wrong, and you have to have the system completely offline, and usually re-index afterwards. In this case, if it is only the history date, then it is safe, as there's nowhere it links to, all you're doing is lying about a historical action.…

Yes, when you clone B, you won't get A's subtasks cloned, because they're not part of B.

Partly. Those two tables are the history of an issue, but I think you will also want to look in the AO tables related to Jira Software - I have a feeling the date things are moved into (and out of) a sprint is recorded in one of them as well.

Have you upgraded all the plugins as well?

You have not addressed anything, just kept repeating that you'd like to do something that would solve no real problems and directly cause problems if done in a lot of places this software is used. I'm not disqualifying anything, just pointing out why it is a bad idea.

I think you need to try reading my point properly, instead of ignoring it.

They listened to their users who do not want people arbitrarily removing themselves from a project. If I were a project owner and you removed yourself without asking me, I'd add you back and then look at how my organisation handles disciplinary procedures for misconduct. 

<sigh> There is no data loss when a person is removed from a project or disabled. As you've missed that, I assume you've not read the rest of the conversation properly and hence have missed the most important point.

See https://confluence.atlassian.com/adminjiraserver/jira-applications-installation-requirements-938846826.html If you are going with Jira Server, then you have no clustering, so neither of your models apply. You can get close to active:passive by having a standby service with replicated data that you spin up on primary…

Yes, that's correct. You need the "for view" message field if you want it to appear on issue view, but the "for edit" version for your message to appear on create, edit or transition screens.

Jira already does all of that, but only project admins can "remove" people from the project. 

Yes, you do need to hack the database to destroy historical data. You can't do it with REST, only via plugin code or changing the database.

Jira supports 1 and 3 off-the-shelf with "email handlers", but because the person is not a Jira user, it cannot know where to reply to, so 2 cannot be done. If you got Jira Service Desk, this allows you to have "customers" who are not considered full Jira users, but do have an account with an email address, and hence all…

I usually use the "message fields" from the Toolkit app to do this. In plain Jira, there is no function that does this properly.