Comments
-
No, this is correct. Jira Core is the "platform", and it is what the footer is reporting on. You have Jira (Core) 7.13.1 The second line in the list of "Applications", the one in blue, says Jira Core 7.13.1, matching the footer, because that's what you have. Jira Software is another Application that has to be installed on…
-
I have a couple of very very very minor disagreements with this post: 1. 5,000 now 5. You can get a "development" Cloud environment, but it is small, no good for any type of scaled testing, or staging, and aimed very much at App developers, so it certainly won't do much for good practice. Better than nothing though. 6. You…
-
This happens when the system is being told that the database is being actively used by another Confluence system. It's often because someone or something has tried to start a second instance of Confluence without waiting for the existing one to shut down completely, but there can be other causes. Work your way through the…
-
And the field name?
-
I think it's a weakness too - I'd like to see the colours configurable ideally, being able to set some form of rules for them. Even the addition of a hard-coded "use the priority colour" and "use the status colour" when grouping by one of them would be vastly welcome.
-
See https://confluence.atlassian.com/adminjiraserver/working-with-workflows-938847362.html
-
Sprints do not belong to projects, they belong to boards. To get a board to only show appropriate sprints, change the filter so that it cannot include issues that might be added to sprints on other boards.
-
Read the links from the current issue with issueLinkManager.getOutwardLinks(issue.getId()) That will return a list, which you can iterate through looking for it.getKey().equals("CPWEB-2056")
-
Yes, you can, Jira is an issue tracker at it's heart. Without Service Desk though, you will have no portals or SLAs, and your issues will be fully exposed to the end-users. You'll need to work hard to build queue-like functionality and reporting (although there are some Apps in the marketplace that can help)
-
Because it was solved when it was asked 5 years ago. There is no solution for Cloud still though, the architecture doesn't allow for it yet.
-
Could you explain what this has to do with Jira?
-
No, it uses one base url - it can't use two or more fully, there's no way it will know which one a user might be using, so it always has to go back to the one it knows it is running on.
-
Sub-tasks take on the security of their parent, so you should store the restricted information separately, either in a project that most users cannot see, or on issues protected with an issue type security scheme
-
Tool, not specifically, but there are some settings in Next-gen projects that could help if you are on Cloud, and it's worth a look in the marketplace for other Apps that may be able to add functions you want in your procurement processes.
-
Ouch, yes, that's a corrupted database. I know of two ways to get there - first, when a Jira bulk delete fails in one session while a project deletion is running in another, and second, someone or something is messing with your database (either someone touched it with SQL, or a badly written script or add-on) The best…
-
Confluence won't really support this. You're running a web-service with Confluence that responds on the base-url and will continue to do so while it is running. By definition, you can't get 404's because the pages Confluence is serving ARE there. But there are some options. Most of us will simply turn off Confluence.…
-
This is pretty much the configuration of the Sophos web safety software - it's been told, on their machine, to block your https site.
-
No, although that would be nice (to save screen space, might be better as a tooltip when you hover over a column name and/or an empty space). Best you can do at the moment is to hover a card over the column, then you get a set of boxes, one for each status, so you know what you can drop into, but that's a clumsy fiddle.
-
Archiving only exists for Data Centre Jira systems at present. For server, you have to do it "manually", by hiding things, as @Tinker Fadoua said
-
what do you mean by "filter options" here?
-
Yes, you should be looking for the cause of the field update, not the processes that occur afterwards. Once you've found it though, I would not see any reason to fire a second event - you already know the field has changed (because the data it is built on has changed), so you can act directly on that, rather than trigger…
-
Next-gen doesn't have templates. You create a next-gen project and then select what features you want in it - boards, scrum, etc
-
The new issue view does not yet support that type of field.
-
No, there is no role of "comment owner" because roles are done at a project level. But the permission does it for you. You could grant "edit/delete own comment" to the entire world, and only the person who made the comment would then be able to edit or delete it. That's the point of "own" in the description of the…
-
Welcome to the community The new view does not yet support that type of field
-
Most of your questions are too poorly defined for a definitive answer, but in general: * Yes * Yes * Define attributes * Define sufficient * Your sentence fragment lacks context and explanation, so it does not make any sense * No because you can always override it in the browser so it's pointless * Define "mapped", "by…
-
The application log will contain the details of the underlying error - see <confluence home>/logs/atlassian-confluence.log
-
It does sound like you logged in with a different account to usual. Try logging out and then logging back in with your usual Jira account.
-
Yes, stories go in the backlog, but the rest of the post is not quite how Jira works. Jira has three layers * Epic - (which is a way of grouping Stories, so you've got that one right) * Issue - usually a Story, but you can create plenty of other types. The name of an issue type is just a label. So you can call them "tasks"…
-
Interesting, but the short answer is "in most cases, no". As a rough guide (this is technically not quite right, but is the easiest way to think of it), a scripted field is calculated when the issue is indexed. And sometimes more than once. The event that goes out when the field changes is actually due to other changes on…