Comments
-
Locked fields are locked by the plugins or core code that needs to protect them from potentially inappropriate change or deletion. Unless Atlassian documentation explicitly says "you need to unlock this field", you should not unlock them. Some of them probably could be deleted safely, but most will break things if you were…
-
I'm afraid you are "hoist by your own petard" here. >One could go deeper an find out the field layout whether the field is hidden or not, depending on the project. However that is way to complicated. It is way too complicated. It is one of the reasons that you should not be trying to do this via SQL - it's hard. To answer…
-
Without Apps, the closest you can get is to clone each issue in project A manually and then move the result to project B.
-
No, you have to be an admin to add Apps.
-
See https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html
-
Your Confluence has two "application links" which are allowing the "insert jira issue/filter" macro to choose between them. For the gadgets, their definitions need to be added to "external gadgets" in Admin -> External gadgets. You've had the filter results and 2d stats added from one Jira, you need to repeat that config…
-
You could make the card colour match the swimlane if you set up the same selection rules for colour and swimlane. But not layout or fields etc - they remain consistent across the whole board.
-
You don't, as we already discussed above.
-
Oddly, Atlassian have docs for upgrades. First hit on a search engine is https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
If you re-install windows, you will scrub the installations of Jira and Bitbucket. The licences will remain valid so you can use the same ones when you re-install them.
-
You need to give it the user name and password set up for accessing that repository.
-
What configuration? There's nothing to configure here.
-
Check that you have the "global permission" for "create shared objects"?
-
Problem is that you've created a custom event, which is not going to get fired by project creation just because you've called it project created. You'll get workflow notifications via it if you use it in the workflows, but that's not going to create projects.
-
Ack, sorry, I'm wrong - no, the security scheme does not recognise the users in scripted fields, even when you've got the right template.
-
I'd judge each case on its own merits - we often did move issues to new projects. You still have to do all the "new" config whether you're moving or flipping the flag. Moving to a new project can mean having to replicate some or all of the current config of the old project too (the further away from the template you use,…
-
Three things I'd look at: * Minor, and rarely a problem (and when it is, it is obscure) - remove the trailing / from the two proxy lines * You appear to be proxying from subdomain.domain.fr to subdomain.domain.fr - is there a reason for that or were you obscuring your data for privacy and used the same thing twice? Either…
-
I recently helped someone change Software projects into both Service Desk and Business projects, for broadly the same reason - simplification. You take a Software project being used for development and then gradually add non-development users to it so they can create their own issues in there without you needing to do it…
-
The things I've flagged as irrelevant are irrelevant because they are part of the service, not things you have to do for yourself any more. The database lives behind Jira - you don't need to think about it. You can't use your own domains or certificates, and the licences are simply part of the service. We're not Atlassian…
-
For most of the answers, see https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html But also * Plugins - you will need to read up on converting each one you have in the vendors documentation (Assuming there is a cloud equivalent) * Support Hours - see…
-
This is a slightly convoluted one, but the logic explains it when you think through the timing. You can not add a user as a watcher on an issue they can not see. That makes sense - it's pointless adding someone because they can't see the issue and hence won't be notified about it either. There's no point watching things…
-
You need to explain what you mean by "server level activities"?
-
See above!
-
What error message is it, and when you're trying to start Jira, can you run "ps -ef | grep -i jira" to see what JVM it is trying to start with?
-
Do you mean as though it were a user-picker? You can if you select the "user picker" template for the script output
-
You could use the REST API to pull down a range of issues that you need, but the best approach depends on what you're trying to "extract"?
-
Go to the board configuration and look at the estimation tab - change the setting from points to hours.
-
Project Configurator is the best option. Although I would say that, as I work for Adaptavist. Trying to be agnostic, the other best tool is Configuration manager by Botron. If you're not wanting to use an App to do it though, you're either into creating your own scripts, or manually re-creating the project in the target…
-
You don't have a transition from the current status into the done status in your workflow. Or you do have a transition, but the "conditions" on it do not allow you to perform it. Check with your admins - anyone who can edit the workflow in full.
-
It's a pain for us too, not knowing when we have to alter training every week. And people seem to like putting training videos on Youtube, which are then rendered pointless within a few weeks.