Nic Brough -Adaptavist- Expert

Ah, right, well that is in the docs! https://confluence.atlassian.com/confkb/how-to-use-apache-as-a-load-balancer-for-confluence-data-center-970602623.html You can skip the web-sockets bit for Jira

https://library.adaptavist.com/entity/show-last-comment-for-an-issue shows you how to get to a comment object, which you can ask for the created or updated dates, as well as the name of the author. Note that "how long ago" is not scriptable - it's a moving target, so you'd have to be re-indexing constantly.

And there you go - the API does not have a variation of classification, a status, relationships with other things or an owner (beyond it belonging to the system you are in). They are not even configured in any way. I am not sure you really mean "API" now.

For a team-managed (next-gen) project, I'm glad to say you can't do it. The system won't let you make that mistake. For a company-managed (classic) project, you can edit the edit screen, and add the resolution. But you must remove it the instant you have finished correcting the issue, otherwise you will corrupt your data.

Well, your searches can have time-based elements to them, those might be helpful. The most obvious clause is quite simple and does what you expect: <date field> = <a date> You can of course then use greater than and less than to do <date field> is after or before a fixed date. (so "updated > 23rd April 2021" means "issues…

This is a question for your load-balancer software, not really an Atlassian thing - all they have on it is https://confluence.atlassian.com/enterprise/traffic-distribution-with-atlassian-data-center-895912660.html I've successfully followed the instructions in there, but it wasn't an F5 as you suggest you're using.

What do think a configuration item is?

I have no idea, that's not an Atlassian thing.

Yes, I've been doing that sort of thing with Jira for years, by * using apps that enable monitoring systems to easily talk to Jira, either apps for Jira or for the monitoring system * with direct interfaces (the monitoring system uses SOAP or REST to push data into Jira) * with pull scripts (things run in Jira and ask the…

You can't do this, it's not how the report works. There are two elements to the report - a search and a display. The search gives you a list of issues that match the question you are asking. That is fed into the display which shows you data from the issues in the list. In this case, your pie chart is looking at sprint for…

That's not corrupt, that's using it properly, but not having a sensible process for correcting mistakes. You've just got a user who had the wrong resolution - that's the "corruption" here, not the process. You could easily reduce the impact of this though - add a transition from Declined to Declined with a screen on it for…

Because APIs are not configuration items.

No, you do not want to do this. Resolution should be empty when an issue is in an unresolved status, and set to something when you move the issue into a resolved status. If you put it on edit screens, it will be set on any edit. This means that you're creating and editing issues that are already resolved/done/ended at the…

It's usually the id you need. I think you should have a look at the project though, the "change" might be that someone removed priority or changed the priority scheme. No priority usually means "nothing selected, field is empty" though, which is usually a null, or not sending anything at all.

Change the email to create another request type, then you'll be able to remove the request type.

What documentation are you following? I ask because you mention using localhost:8900 which is, as far as I know, never mentioned in the docs - 8900 is not a port any Atlassian software uses, and localhost is always going to be Server, never a Cloud system.

We need to ask the community admins for new groups. I've asked in leader's Slack!

This means your Cognito system is not responding to your Confluence server's requests in a way that it understands. The Confluence log will probably contain a bit more information about the problem (i.e. what the Cognito service said back to it), so having a look at them might help - see <confluence…

You do not. You could try hacking the core of SD's code to stop asking, but that would be unsupported and a big security hole.

If you don't want a particular request type to appear, remove the request type.

What do you mean by "integrate"? What exactly are you trying to achieve?

No, you cannot @mention people in comments that might expose them directly to customers in a request.

It might. Depends on what you have added to the transition that might change it. I don't think you are quite grasping the most important point here - you need to set/clear a resolution as appropriate for your process. We cannot tell you what your process is.

I can remember four 'phone numbers. My current mobile one that I picked up in a shop in Canary Wharf where it was £100 cheaper to get a new one than carry the old (and given the 'phone was under £200...) Canary Wharf dates that one back to the late noughties. My home land line, which I use to a) have internet b) deliveries…

Hmm. >Screens that do not show the correct status of issues are problematic. That really needs to go straight to Atlassian, no screen should show an incorrect status (after a refresh at least) >The limitation that it does not follow the Scaled Agile Framework for Enterprise (SAFe) Hierarchy is, however, a real showstopper.…

Oh, and I forgot - the technical reason that there are three lines in the database for version is simply that those are the upgrades that this Confluence has been through at some point! Those are not strictly upgrades triggered by an admin, a lot of the upgrade packages actually don't re-invent any wheels, internally they…

To be fair, sometimes, it can work (most important is that the database structure has not changed between the current and older version). But it's a world of hurt getting it there and being 100% sure everything is ok. Absolutely right about "interesting ways" - the one that taught me that lesson was not so much a downgrade…

You should not be messing with the numbers in the database (in fact, just don't even look at the database) More specifically, in this case, you say "which means, for Confluence, installing a lower version than was already installed.". Nope, don't do that, downgrades often completely fail and mess up the data in interesting…

The "create issue" screen is a form. Work out what fields you want to report on, and add them to the "create issue" and probably "edit issue" screens.

So not a ticket, but definitely a request. In the "reply to customer" comments, you should not be naming people - the customer does not get to see who might be assigned or mentioned on the issue or request.