Comments
-
Right. "Jira Service Desk" is not Jira, and it only works on Jira 6 and 7, so you can at least rely on the recent docs for the types. However, it's quite likely that a load of your fields are Service Desk fields which have their own keys again. The thing here is that you don't need to get them totally right, just right…
-
I don't think your workflow is asking the user for a resolution, or setting one automatically. Jira uses an empty resolution to say "issue is open", it doesn't work off status. (Beware of "Jira Software", which uses that as well as "being in the right-hand column")
-
Our messages crossed. Yes, that doc should give you the keys like the "com.atlassian.jira.plugin.system.customfieldtypes:datetimefield" I used in my example - many of them might be the same as the Jira 7 I'm looking at. I just know that some of the fields definitely changed in version 4, and that might have affected the…
-
No, they were not, it was one of your SQL updates that trashed them. There is no way to know what they might have been - you are going to have to guess based on the field name and the contents. You've said you were on Jira 3.15, which doesn't exist, so I can't begin to tell you what the customfieldtypekey might have to be…
-
There is no default key - it is different for each custom field. You can take a guess by looking at a custom field value record for that custom field though - if the data says number or date, you know it's one of those and might be able to work out what a matching key is by looking at another field of a similar type. (and…
-
Start creating projects, the project templates will create the basics for you. Even when I'm not going to be using anything like the projects Atlassian have templated, I start with them because they're going to give me a better starting point than <nothing>
-
That makes it more difficult again, but it is possible to recover a complete Jira from a backup of the database and a copy of the attachments. Do you have those? (Database backup literally means a backup of the data, using the db tools to do it, not the xml copy)
-
No. That will not help in the slightest. You need to undo all the SQL damage you've done, putting the fields back to what they were before.
-
That's because you set it to that. It is wrong. Even if it weren't misspelt, it's being truncated down to a module that definitely does not exist. You need to set back ALL of the custom fields customfieldtypekey to what they were before. The searchers are less important because they can be fixed in the UI, and wouldn't…
-
There is no "native" way. You need javascript hacks (not recommended and definitely not native) or Apps.
-
No, as they're totally different feeds of information!
-
You can try injecting javascript, but it's rare you will reliably catch all the places you might be able to edit. I would strongly recommend getting an App for this sort of thing. Ideally one that provides a field that can be limited internally, not with js.
-
Start with the logs under <jira home>/log - look for "atlassian-jira.log".
-
Nope. You'll need code to add the web-panel.
-
Stop Jira, change the keys back to what they were before, restart it and run a full locking re-index. This SQL only works when the field types hold data that are 100% compatible, and I suspect * They are not * sysme is not a valid custom field type
-
There is an App that can do it for server, and it has the rather useful default of "don't allow people to mention the login groups"
-
Projects do not have fields, so you'll need some code to do this. If I need project fields, I tend to look first for the "profields" App to do the work for me.
-
Sorry, I was not clear there. There are no scrum estimates for sub-tasks. You can still estimate time on them, but that will not be of any use in your charts, which is why I said to use Story Points instead. If you want to base your scrums on time estimates, you can, but you will need to abandon time estimates on sub-tasks…
-
Yes - see https://confluence.atlassian.com/confcloud/migrate-from-confluence-cloud-to-server-724765578.html
-
No, your Software licence entitles you to Core as well. However, Core is a manual update - you have to download it and run the installer, telling it to upgrade your old Jira.
-
User macros are only available to Server users, I'd guess you are on Cloud?
-
Run a filter/search for "in review", and maybe think of having a (Kanban) board that shows it separately.
-
Yes, you will need an App (plugin) to do this. The built-in cascading select list only supports name and description there. If you want to add more data around it, you will need to * Provide somewhere to store the new data * Provide screen(s) to maintain it * Provide a way to get it in front of the user when a screen with…
-
For an issue to be considered "done", and counted by burndown etc, it needs to be in the right-hand column on the board. You'll need to move "in review" into the "done" column to achieve this.
-
For plain Jira, you could create a user to use with the API and then limit transitions with "only my API user can use this transitions". If you're willing to use Apps, there's a few that have that condition already, and a couple that have "hide transition from logged in human" explicitly
-
Yes, but sprints also get generated by boards, so even when people have different board settings, the sprint data is still based on the right-hand column for their board. This can let you set up things like: * Workflow: To do -> In dev -> dev done/ready to test -> in test -> tested * Developer board: To do -> In dev -> dev…
-
Ahh, excellent. I asked because the output templates determine the types of search. A text field gives you a text search, but they're a bit rubbish on exact matching and fuzzy searches with numbers in my opinion. While stuff like "~ flibble" or "~ pingu" will get you searches related to penguins, "~ number" often returns…
-
Not really, that's a scrape of the documentation most of us use if we're not using Insight. Where are you stuck with it?
-
See https://confluence.atlassian.com/adminjiraserver/working-with-workflows-938847362.html
-
I mostly see it used as Atlassian built it. You usually estimate stories with Story Points, and then when you need work logs, you add them to sub-tasks and stories as needed. You don't put scrum estimates on sub-tasks, because you don't commit to sub-tasks in scrum, you commit to a story, and a story is either done or it…