Nic Brough -Adaptavist- Expert

For blogs, I'm afraid it's checking in regularly. Atlassian have some mailing lists and RSS feeds dotted around too, but I'm not sure any of them report on new blogs. https://developer.atlassian.com/platform/marketplace/early-access-program/ may be of some use

I suspect you need to move it up two levels - set the resolution before creating the issue. Although, I really want to question what you're doing. Are you sure you want to be creating closed issues that need no further attention?

Nope. I'm not an Atlassian. It's not Atlassian who judge it either. I had two meetings today where security issues were discussed and one client's significant security concern is another client's "that's not a security issue". CVEs are a good indicator, and I'd say "if it's a CVE it should be a security issue", but there's…

Text doesn't have an exact search, you shouldn't need it. But it does have a fuzzy one. You can create swimlane filters for things like "summary ~ <text>" which may be able to group correctly if the strings are distinct enough for the fizzy logic to catch.

Jira renders users inactive rather than deleting them because the user may return and it may have data that Jira needs to keep an association with. (By the way, you should never reuse an account identifier such as a user name - it's a breach of a lot of auditing and compliance rules, and possibly GDPR, not just a bad idea…

Atlassian don't engage in activities like this, they will simply refer you to their online documentation. Some of their partner companies (one of which I work for) do do this sort of thing. You can probably find a good one over at https://partnerdirectory.atlassian.com/ especially if you picked a French-speaking country,…

Start by defining what TMG is - don't assume everyone knows what every acronym might be. Trimethylglycine, Tiny Meat Gang and literally just TMG - a compiler language older than I am.

I suspect you are on an older version then, from before the home directory was restructured to be the same (this is quite a recent change)

This doesn't hide the fields from people at all. It just protects editing a bit.

Licences are not assigned to users. Licencing is a simple cap on the number of users. You give the system a list of users you want to let in, which is one or more groups of people. Your new user needs to be added to that "can use the system" group.

You don't need to request anything, the REST API is always available. You'd know if it wasn't - a lot of stuff stops working if it is blocked. Start at https://developer.atlassian.com/server/jira/platform/rest-apis/

No, it's not available for Cloud. To destroy the history, you need access to the internal java API, Cloud apps do not have that access.

There's not one I know of. A few under https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=test are free, but they're all aimed at one very tiny part of what I think of as "test management"

Even if you "optimised" it, you'd still be getting 90% of the release notes, there's almost always something in one that someone sees as a security thing.

IssueManager.deleteIssue (user, Issue, eventDispatchOption, boolean) should do it. the eventDispatchOption should probably be ISSUE_DELETED and the boolean is true/false about whether to send email.

Jira is an active service, not a passive data store. You will need a completely different local store to work on "offline" and sync later. One option would be to have your own Jira running on your own machine, running with an app that can synchronise between your local Jira and the main one. This is expensive, clunky and…

There is no logical way around this. You can't translate from system to system and preserve field keys because the ids have to be unique. The only logical way to avoid having to edit the scripts for the object ids would be to have an arbitrary global id scheme something like "a hash built from the date, time, and licence…

Ahh, monitoring, always a good thing! I suspect the Prometheus exporter is pretty much doing what your SQL is doing as well, it's not interrogating the code, it's looking at the database. I don't think you're going to be able to build what you need without doing some coding. I'd think about using script-runner to create a…

This is because status is not a field and you do not edit status. Status shows you where the issue is in the workflow. You change it by triggering transitions, not editing. To do what you're looking at here, you will need * A workflow that has a transition from the current status to the status you want to go to * Something…

No. Apps have to match the size of the largest application you have (if you had 100 core, 250 software and 5 service desk agents, you'd need to licence apps at 250, not 500 to include 355 users)

I think we're still struggling to understand why you think you want to do this. When a sprint is complete, it's complete. It should not change the status of anything in it, it's not what determines where an issue is in its process. It actually reads the status to decide whether something goes to backlog, next sprint, or…

No, for both questions. This is one of the reasons I tell people to not bother looking at Atlassian databases - they are a data store, not suitable for reporting, and quite often don't contain the data you are guessing they would. 1. The database is useless here because the type of installation is worked out by code when…

Done is the last column on the board. You can put whatever status (in whatever status category) you want to done, but you can't change "last column = done"

Yes. Do you still need anything about "safely"?

No, I'm afraid you just have to follow the general Bitbucket blog as mentioned on https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/

>I change the status of a subtask by moving it around in the board it updates, I go back to the initial state. If it disappears from the board, how are you doing this move back to the previous state with it?

Ok, let's rule out the xml for now. To move Confluence on another server, let's look at the minimum viable backup. You need a copy of the database somehow, and a copy of the attachments directory. With just those two items, you can recreate a new copy by * installing Confluence empty, * installing (but don't bother…

Neither of those will work. Your version of Jira is way too old for the importers. If you want to use the direct import, you will need to upgrade to at least 8.0 and I'd strongly recommend 8.13 over 8.0. The Cloud migration assistant only works with Jira 7.6 and above, and again, I'd strongly recommend going to a much…

The best way to do this is to upgrade the 6.4 and then copy the resulting system on to the new server. Or copy the current 6.4 system to the new server and upgrade it. The second best way to do this is faster, but may not work - take a full backup of the 6.4 (the built-in xml backup) and import it into the new system. It…

You would need to rewrite the gadget so that it can arbitrarily ignore data that you don't want to see. Before you question that, it is worth explaining why I've said that. A search (a filter is a saved search definition to re-run by things) returns a list of issues. It does not return any of the data in the issues, it…