Comments
-
This is somewhat provocative, but maybe review why the security scanners don't understand what these methods are for and why they're not dangerous when used correctly? As they say, they are "auth protected" in Confluence, and are hence used correctly. So I'm a bit confused on why they have reported this to you like this.…
-
Please see the answers to https://community.atlassian.com/t5/Confluence-questions/Is-ccoewiki-tapestry-com-application-using-log4j-utility/qaq-p/1888492 - they contain links to the articles and conversations you need to read.
-
Last time I looked, this was referring to whether the resolution on the issue was set or not. Jira considers the resolution field to be the done/not-done flag on issues. If the field is empty (in the database), then the issue is not resolved, and displayed as unresolved. If any value at all is in the field, the issue is…
-
No, it could well break Bitbucket, and it would render you unsupported. I'm assuming this is in response to the CVE - see https://community.atlassian.com/t5/Trust-Security-articles/Atlassian-s-Response-to-Log4j-CVE-2021-44228 for the guidance on what to do.
-
Start with a read of https://community.atlassian.com/t5/Trust-Security-articles/Atlassian-s-Response-to-Log4j-CVE-2021-44228/ba-p/1886598#M134
-
Welcome to the Community! Trello is a service, not something you run yourself, so a simple answer is that you do not care. It's Trello's/Atlassian's problem, not yours. On top of that, the vulnerability can only be exploited by "An attacker who can control log messages or log message parameters", which is effectively…
-
Yes, that's exactly what Epics are for - going across projects.
-
No, you can not. Your licence for 100 users is for a single production server (or DC cluster), it is illegal for you to use it on a second production system. If you have a second system, you will need to buy another licence for that. (This changes a bit if you have Enterprise licences, but it's unlikely you'll be looking…
-
There is a long-standing bug in the workflow editor that the draft mode cannot add transitions to a step that has not already got at least one. The work-around is to not to work on a draft - * take a copy of the workflow you want to edit * add the transition in there (and make any other changes you need * save the workflow…
-
It won't do that - the point of Epics is that they can be cross-project items, for gathering together larger pieces of work, or groups of stories.
-
There's no attachment of the error message. But my guess is your Tomcat hasn't been configured to tell it that you are behind a proxy/load-balancer. Have you put in the proxyName, proxyPort and Scheme? How is the load-balancer configured?
-
You can get started at https://support.atlassian.com/statuspage/docs/get-started-with-statuspage/
-
Correct. It's not actually a bad assumption, especially for a Jira that hasn't had many "clever" things done to it, either by code, apps, or even database hacking. But most of the ones I work with have had something "clever" done, and we often find the ID is not a reliable sort order for all sorts of bits of them. Inside a…
-
It used not to, but I know Atlassian changed something related to it a while ago. It might have been components though, or not the move process. It is absolutely worth a try!
-
Welcome to the Community! This code is not really an error message, it's a label for an error which may be affecting many Cloud systems, and is being used by Atlassian to identify the affected systems and group together any support calls they get about it. Best thing you can do is report it to Atlassian at…
-
No, you can't do that. Versions are a project artefact. If you move an issue from one project to another, the new project has its own set of versions, it can't apply a version of another project to its issues.
-
Ah, hang on, I thought you'd exposed the actual issue id in a field, which would override the alias here. So, we are looking at the key, in which case, I'm stuck on what the problem is, the JQL is returning the right data, sorted in the right order. What you're asking for is still going to be incorrect, as looking at the…
-
Hmm, my last answer vanished, but it was about the screenshot and explaining something else. No, I was pointing out that there is no Epic field in Jira, and that frames the answers already given. That's not indirect. The "add epic" in the question is not an Epic field, it is a function to create and/or link to an Epic.…
-
The order you are getting when you sort by ID is mostly going to be the same order as the keys when you look only at a single project. Again, the ID is not the key, it is not purely sequential, and may not even be in creation order in some cases With your limited data set (single project, nothing clever that might be…
-
This will have put an error in the application log - Jira-home/logs/atlassian-Jira.log
-
Ok, there's a couple of things here. First, your queries are for "ID >", which is simply going to return a list of issues created since an unknown point in time. Your report specifies no order, so the issue navigator is defaulting to sorting by the issue key. The search and the report are separate things (although there is…
-
I do not think I understand the question or requirement. If you stop people re-ranking in the backlog, of what use is the backlog? It sounds like you want to turn off ranking (which you can do, just change the "order by" clause in the board filter to something other than "rank")
-
Welcome to the Community! Status is not a field you can enter, it's an indication of where an issue is in the workflow. You can't edit status, you have to transition issues from one status to another. Automation can do this, you have to select a "transition" action instead of an "update field". Where I think you might be…
-
Ok, filter should not be a problem at all, although as a side question, does the filter return issues in the issue navigator? I think the index might be broken, is it possible you could re-index the project? (This is why I asked about Server - your admins can only re-index on server)
-
What is the rest of the query for the board? Also, are you on Cloud or Server?
-
The ID of an issue is the unique key for it in the database. This table is not divided by project, every new issue gets a key id a bit higher than the last one, irrespective of the project or anything else. Also, they're not sequential, you will find you've got gaps in the numbers. The ID is simply the wrong thing to be…
-
I think the docs on this are not very clear. Jira has two real uses for screens - viewing an issue and editing it. "Message fields for view" only display on screens that are for viewing an issue - that means the issue view, navigator and reporting. "Message fields for edit" only display on screens used for editing, and…
-
If this is Cloud, you will need to raise this with Atlassian support over at http://support.atlassian.com/contact If it is on a Server/DC install, then you should read the logs to see what is going wrong.
-
It means people who have not logged in will not be able to see any pages.
-
Yes, see https://developer.atlassian.com/server/confluence/confluence-server-rest-api/