Comments
-
No, I'm afraid a field configuration starts with the assumption "show everything". I would take a different approach and do it with screens. As "create new screen" gives you a screen with no fields, you can just add the ones you want. Personal opinion on context, field configs and screens: field configurations "hide"…
-
Code, and quite a lot of it. Status is not a trivial "field" with a bit of data in it. Jira is built on a workflow engine designed to track your process and status is a very important part of that. A drop-down simply is not good enough. You would need to think about all the conditions every time somebody clicked it, and…
-
Ah, that would be it. Kanban boards work off fix version, and rely on "fix version is empty or unreleased". If you remove the fix version, they can't answer that question, so they have to assume the issue is not for the board. You can get rid of most of that - have a look at the board configuration and you'll see the…
-
Not strictly Atlassian, but I left the BBC to join Adaptavist. My boss knew I knew Altassian stuff, but had not really done much "real" consultancy, so he took me to shadow his next gig. My first engagement as a Jira consultant was for, um, the BBC. To be fair, most people don't know the BBC is effectively two separate…
-
Possibly. I'm not that familiar with it, so I don't know the capabilities. If it requires database access, then I would run away screaming. You will have to build and maintain a detailed database dictionary, and that's a bloody nightmare with Jira. If it can make queries of Jira over REST, then, while you'll still need to…
-
I am afraid notification schemes are project level, so you can't do this. Yet. There is an open request to move them down to issue type level somewhere, and Atlassian seem to want to do it, but I remember it's not a high priority, and it's not in my bookmarks, so I'm not sure where it is.
-
I don't usually do code, as it's better for people to learn for themselves, but in this case, it'll probably help you to see the raw code! issue.getCustomFieldValue(customFieldManager.getCustomFieldObjectByName("user picker field name")).getDisplayName()
-
setenv is the right place to adjust the memory! There are other places you can make it work, but setenv is "the source of truth", and the first place every Atlassian admin looks.
-
I think there will have to be - there are a lot of people complaining of search being broken today. Missing search on the nav bar is another thing (It's one of three things I really hate about the new layout on Cloud)
-
There is no way to downgrade a Jira system (unless you're willing to put in months of work converting the data to the previous format)
-
Get the backups you took before you upgraded. Install the previous version somewhere, and import the backups.
-
You can't do this in the UI, you have to either code something (script) or amend the database directly.SQL is probably the quickest and easiest approach, and it's one of the few relatively safe things to do in a Jira database.
-
You'll probably want to start by giving a little bit of an idea of what Helm and k8s are.
-
That's not available on Cloud though, and I don't know if there are other add-ons that could do something with Cloud.
-
If you are using the standard off-the-shelf Atlassian accounts, then no, you can't configure the passwords. This is because the accounts do not belong to your organisation, they belong to the users, and are used for all Cloud systems. I use one Atlassian account for access to around 30 Atlassian stacks my clients have.
-
Not natively, but you can use in-line comments to get close, or edit the page and format the content to highlight what they're looking at.
-
No, that is a front end which takes you to a portal only when it's identified the right one to use (and a number of options don't take you to portals) It's doing pre-filtering as Atlassian only use portals for certain types of request.
-
You can extend trials, but only a couple of times. See https://confluence.atlassian.com/purchasing/how-can-i-extend-my-evaluation-321257637.html
-
Yes. Look at the "field configuration scheme" and the "field configurations" in it. You need one FC with Description set to wiki and a second one with plain text. You then need one FCS for each.
-
Ok, that's the problem. You've got DC licences in place and you're trying to install a Server licence. The licence types cannot be mixed. I suspect you will need to blank out the evaluation licence for Service Desk, rendering it inactive (this does not remove any data, just stops the functions working), then you'll be able…
-
You can't vote for closed issues. There's no point, Atlassian have said they're not going to do this (but are going to allow more control delegation to multi-select fields)
-
@Jake Yemtsov- no problem, I just didn't want people to think that Champions like me always agree with Atlassian. It's the right model of access, the principle is simple, but I despise Atlassian's default and it is either complex or tedious to fix it after a system has been growing for a while. As for your cross-posts,…
-
Yes, because they don't need or want it. There were very few votes on the issue in JAC as well, compared with other requests.
-
No, I did not say no then yes. I said you can't host Cloud systems on your own kit in answer to your questions. Then I talked about migrating your data to your own Server install. Start at https://www.atlassian.com/software/jira/download (click the pricing to see how much a server licence will be for you. It's a LOT…
-
No. Cloud and Server are different products and you can't install Cloud on your own kit. The data is compatible between the two. As you already suspect - get a backup from your Cloud server and you'll be able to import it into a self-hosted server version. The functionality will be different (mostly in terms of layout),…
-
You would have been given the contact details when you signed up for premium support. If you don't have premium support, then support is done through the Service Desk (except for $10 licences, which are diverted here initially)
-
I have never claimed that it is simple to implement. The principle is incredibly simple: do not give access to people who should not have it, give access to those who do. implementing it is daunting for an admin who has not yet fully grasped how permissions work, and very dull and long-winded for those who have got it.…
-
Could you take a look at one of the issues that should be one of the 10 "in progress" - does it have a fix version set?
-
Ah, I see, sorry, the edit confused me a bit and I compounded it by misreading things. Could you go back to the "Manage applications" screen and check what licence types you have for each application?
-
Unfortunately, you can't swap to a list view in the project reports. You have to go to "issue search" (the issue navigator) and run the search for open issues (or other) in your project, and then you can swap between a similar view and the list view.