Comments
-
Ah, I see, I misread it. As long as "unresolved" is not being selected from the field, I'm happy.
-
There should never be a default value of "unresolved". I think your Jira is broken.
-
Permission and security schemes do not apply to Next-gen projects. I have a feeling they never will.
-
Could you show us the current sprint board data? (feel free to blur out summary/description text, we're interested in column content, not the individual issues) Also, what are your estimation points? Estimates, Story points or another numeric field?
-
It's more than "change a bit of config", but not a scary amount. Essentially, you make the server into a single node, and then start adding the other nodes you want. See https://confluence.atlassian.com/enterprise/moving-from-server-to-data-center-953127136.html
-
Sorry for the delay, I lost track. I think we need to look at the full history of an issue that moved to a new sprint when the old sprint ended.
-
The way this question is phrased leads me to think of a couple of unusual things that you might have got. >For a specific Jira project the default value 'unresolved' of the field 'resolution' does not appear. The field is empty. At other Jira projects the default value 'unresolved' is automatically set when I create a…
-
Because @MichaelO has seen it happen with a specific browser with specific settings. That's not a server side issue if it is just that one browser with a problem.
-
You will need one of the automation or scripting apps that can read the current assignee and put it in the custom field as a post-function. If this were ScriptRunner, I would base it on https://library.adaptavist.com/entity/update-the-value-of-a-custom-field-in-jira
-
To fix the server side, try going on to the server and using route checking and lookup tools to see why it cannot reach Atlassian. I'm only familiar with tracert and nslookup, although I know I need to learn the newer commands for it. If you are pasting a valid licence into the licence page, I'm not sure why it would give…
-
There is no description of a problem that I can find in this post. You say a transition screen does not display correctly, but the pictures do not tell us what is actually wrong with it. Could you explain the problem a bit more? Maybe concentrate on one field that is wrong, explain what it should do and what actually…
-
There is no way to do that with nFeed fields as far as I am aware. You would need a function to do it (not just a simple call to a field), but I don't think nFeed provides one. ScriptRunner could do it for some field types, but I don't believe it supports nFeed field (yet)
-
I think there should be a big red box in the docs saying that h2 is only suitable for demo and test type actions. It is there in the install guides, but there's no highlighting. It does briefly warn you during setup, and if you log in as an admin, it will give you a "database healthcheck failure", assuming you're on a…
-
The advanced search does not do the same level of context checking that the basic one does, it lets you put in fields that might not be valid for the current project/issue-type in case what you're typing later might draw it in.
-
Yes, you will need to do a server migration first if you want to only take some data. Or, possibly easier, copy the source, delete the projects you don't want (and any spare config), and then use that to create the Cloud system from. For server, If you don't have a licence for the product you are importing into, the import…
-
Somewhere, but I don't have it bookmarked. It affects only admins who have inherited systems where previous admins were unaware of the bug, there's a relatively easy fix, it's actually a lot of work to fix, and Cloud is moving away from workflow editing in this way anyway. So it's very far down in Atlassian's priorities.
-
You need to add a clause to the board filter to exclude the issues you do not want in the "everything else" lane. This will clear them off the backlog as well, as that is what a board is for - looking at everything included by the filter. But as you've got filters for the three swimlanes you have, you can probably just…
-
No, in most cases, people don't want to assume that just because a story starts, the sub-tasks automatically follow. It's perfectly valid to have a set of sub-tasks that have not been looked at, even though their story may be well be quite a long way through its own process. So Atlassian have never put this sort of…
-
Have you tried running it in the ScriptRunner console and check the logs it gathers as it runs? My best guess is that it's either going to show an error opening the file, or the null is what you'd expect as the script has no output to go to the screen. (System.out.println is dropped into the logs, not the screen)
-
The 0.5 at the bottom right is what the board is working off. If you don't want the other one, remove it from the card view in the board settings.
-
Ok, you have two problems here. At some point, you have changed the memory settings for Jira, and it looks like you have set it too low. You will need to change the settings in <Jira install>/bin/setenv.bat to correct this, but possibly also alter the service settings if you're running it as a service. The second problem…
-
Change the field configuration (assuming a classic project). See https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html
-
Oh, that's not good. The best way to do this is use sprints properly - close them when they are done. If you've got issues going through many sprints, then they're sized incorrectly and should be moved to Epics, then broken down into stories that do fit into sprints.
-
First, you need to know what database you set it up with. Did you select the "internal database, not suitable for production"? Or have you installed a (supported) database server for it somewhere? You are going to need to understand the dbconfig if you cannot answer the question above - go to <Jira home directory> and look…
-
No, there's no way to do this. Ranking used to be numeric, but had to be thrown away as it does not work properly and does not scale ether, so it was replaced with the current ranking field. Ranking only works for rank type fields, which are not numeric. If you did try to use a non-rank number field, yes, you can sort by…
-
This is quite a hard one to answer here, as we're an Atlassian community, so we're mostly going to tell you that Bitbucket is better and you'll feel like ignoring us because we are biased. Yes, you should, ideally, pick one or the other. Don't mess around with synchronising or replicating - if you're going to use…
-
A lot of us do this. Start at https://confluence.atlassian.com/adminjiraserver/switching-databases-938846867.html for how to switch databases. Your configurations will remain the same, most (possibly all) of them are held in the database which won't change, and the ones you may have done on the server side won't change…
-
It does not recycle page ids, they just keep going up (I once had to dig this out of the source code years ago). There are some things which can get broken which can lead to duplicate page IDs but they're not common. Pages can have the same name though - once a page is deleted, the "friendly" name of it can be reused in…
-
Mostly that list is fine, but I would not bother stopping Production. Just paste in the developer key, so it becomes a dev/test system (Although you should also do something about warning your people that it is becoming a test system!). Pasting the key in the UI is a LOT easier than trying to mess around with file and…
-
@Andrew beat me to the links you need for the REST API. As they say, you have no database access to Cloud anyway.