Comments
-
I'm not fond of it either - I'd say the link to "other versions" should give us the list directly. Or go to a list of the major versions in one go so we can expand down into them. Having 3-6 in one place and then 7 three clicks away is totally counter-intuitive to me.
-
Click on "all server versions", then "view all", then the drop-down lets you select between all releases of 7.x
-
I tend to use a mix of post-functions (for when I want to update fields) and scripted fields (for display only calculated data) Get started at https://scriptrunner.adaptavist.com/4.3.1/jira/recipes/workflow/postfunctions.html and https://scriptrunner.adaptavist.com/4.3.1/jira/recipes/scriptfields.html
-
Did you stop Jira before doing it, and make sure your database client was the only user active with it? What was the output or response when you ran the SQL to set the flag?
-
I've done this many times. Initially with code providing calculated fields, but later with ScriptRunner (which saved me having to bundle stuff into add-ons). These all looked at the data the users were entering and built risk scores (and other fields) directly from it. There are some risk calculation add-ons which might be…
-
The products are diverging. Last time I spoke to an Atlassian about the Cloud UI going to server, it was "unlikely to be even announced before the next US summit"
-
No, go to "manage applications" in the admin interface and add the Service Desk in there. You have closer integration when you're using SD and Software running in the same Jira Core.
-
You can use the xml export and import, but for a medium to large Confluence, it's probably going to be a lot faster with a database restore.
-
There might be something in the audit log (it's part of the admin interface), if logging was enabled at the time. Jira used to ship with a standard set of tasks and sub-tasks, but now it creates the ones it needs when you start creating projects. That code definitely does not create standard issues with the name of…
-
That's not true. If you have a type called "Sub-task" that is a standard issue type, then you or one of your administrators added it. Sub-tasks off the shelf are sub-tasks.
-
I think Steven may have been replying in the spirit of the question. 4 hours to create a document in Confluence is either the user being facetious or saying that they don't know how to use a computer.
-
See https://community.atlassian.com/t5/Confluence-questions/Update-Test-Confluence-with-Delta-change-till-today/qaq-p/675433
-
* Stop the test confluence * Drop the database tables * Restore the database from a backup of production * Synchronise the attachments from production * Restart Test * Re-index it
-
I can't tell you more than this because there's so much you could do. You don't need an Atlassian account for documentation and information. Other than that, all I can really do is tell you to use it when you need it.
-
Yes. Remove them from the "edit" permission.
-
1. An Atlassian account gives you access to Atlassian systems - i.e. their documentation, support, the maintenance of licence information and payments, and you can use them for logging into Atlassian Cloud systems. 2. Go to an Atlassian system, select "create account" when asked to log in.
-
When you create a new project, Jira put groups into roles in the project by default. Have a look at Admin -> Roles to see (and edit) the defaults
-
Ok, it's a Cloud install, and we need to be looking at logs. Only the Cloud admins can do that, I'm afraid this needs to go to https://support.atlassian.com/contact
-
No, only admins can use the importers. There is a lower level project import though, usable by project admins (For Server users only, it doesn't work on Cloud) A question though - why the need for lots of imports?
-
Not really. The problem is that you really want to record time and the only way that counts in Jira is a work log on an issue. Doing anything else means Jira won't know about it. A lot of places log one "meeting" issue per sprint, or, when they have a regular cadence (e.g. planning + standup + retrospective all add up to…
-
Trello doesn't have this concept. Jira does.
-
The error means Jira cannot talk to itself over its base url. In this case, it is not presenting valid certificates to itself to connect over the https url you've got.
-
Only if you're on a REALLY old version, where there is a bug.
-
Rubbish. They do.
-
Yes, it is, you just need to map the field in the import settings.
-
You need to go into your profile, not just look at the menu option.
-
It doesn't work because Jira needs its data to be written into it via the API. You should NEVER write to a Jira database when it's running, and when it's offline, it's for very specific bug fixes. You should revert your database to the backup you took before you made these inserts, throw away your SQL and never look at the…
-
Admin rights give you admin rights. Issue rights are separate to admin rights, and you need to be granted them separately. Please, read your permission scheme for the project. It does not say "admin can delete" or "project lead can delete" (And rightly so, deleting Jira issues is a bad bad thing to do most of the time, but…
-
I don't know where you're looking, as Cloud has been able to import Story Points since it started. Please, try again, you're missing something.
-
It is definitely a custom field. Most of the Jira systems I work with do not have it, and it is not there when you install a new one. Could you maybe look at an issue that has a value for it in the UI and then make a REST call to fetch the same issue so we can see that it is there and how it comes out?