Comments
-
Where something is part of the workflow, it will be brought in. Things that are just used by the workflow like screens and fields will not.
-
Um, workflows. They export and import workflows. That's all.
-
That's quite a complex one, which I can't quite do without code. However, the way I would code it is to have a user-picker field which is filled with people who meet one of the criteria. You could get most of the way there by using the "participants" field from the (free) JIRA Toolkit add-on. That combines a list of…
-
The lock file indicates that the system is already running. It stops multiple starts. However, it can be left behind if you kill Confluence improperly, or your system is shut down uncleanly (and in some cases, a simple crash in Confluence can do it) Make sure Confluence is not running, remove the lock file, then restart…
-
I wouldn't try it, it's a massive rewrite, and Atlassian are going down that road already.
-
No, you'd need to hack apartall the permission code and rewrite it. Atlassian are moving towards giving project administrators more delegated power, but it's going to take a log time.
-
You can migrate an entire Cloud instance from one place to another, but it is a destructive migration, it will overwrite the target system completely. See https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html Copying over bits of configuration,…
-
Have a look at https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html A lot of it is about changing passwords and groups etc, but there's also instructions on changing the order and enabling different directories in there.
-
Service Desk 3.5 is quite recent, so it's probably running on JIRA 7.3. Check out the "manage applications" admin section or "system information" to confirm it. For 7.3, you're fine on PostGreSQL 9.2 upwards - see https://confluence.atlassian.com/adminjiraserver073/supported-platforms-861253018.html
-
You'll need to find or write an add-on that provides another gadget that can do this.
-
What do you mean "throw their email to @group"? Are they sending to a group address? If it goes to a group or list address instead of JIRA's email address, then how are you trying to get JIRA to pick it up from the support mailbox?
-
You have to work backwards. By definition, a transition only has one end point, so you can't do "somewhere to all", they have to be "somewhere to <single target>". You'll need to create one incoming "all" for each status.
-
There is nothing like that in JIRA, it must be something being provided by an add-on. Have you removed or upgraded any add-ons that might be providing the function?
-
Ouch. That sounds broken. You could take a separate approach - run a temporary JIRA to do the accounts stuff, while you work on getting the real JIRA working. Assuming the accounts are not going to change, once you have the real JIRA working, you should be able to just flip the Confluence over to it.
-
The systems are technically two toaly separate services, so yes, you can start using one without the other. The sticking point is your delegated user stuff. You'll want JIRA running and hooked up to AD, so that it can provide the user data to Confluence. However, this is not actually a huge deal, to my mind. You could run…
-
I assume you don't really mean "delete", but just "blank out or empty the date of a field"? A scripted listener is the best way to do that, it can listen for issue changes, check if your employee field has changed, check the new employee's category and set the customfield value to "null" if appropriate.
-
I'm afraid there's nothing for cloud that does that.
-
Best advice - don't. It's hard to maintain, harder to get right and generally the wrong solution. If you insist on doing it, then building your own add-on is the only real way to do it.
-
It sounds like you might have some form of "locale" mix up, where JIRA is getting confused by different settings, but I'm really not too sure. I've not seen this problem before, and I'd be tempted to go to atlassian support for it ( https://support.atlassian.com/contact/ )
-
There is no whitelist on the Atlassian side. See https://confluence.atlassian.com/confeval/other-atlassian-evaluator-resources/can-i-restrict-by-ip-in-atlassian-cloud
-
No, as I said earlier, it's being removed. You will have to bundle your javascript into an add-on and deploy it properly.
-
Yes, you can do that with a script. The snippet I have is import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.label.LabelManager def user = ComponentAccessor.jiraAuthenticationContext.getUser() LabelManager labelManager = ComponentAccessor.getComponent(LabelManager) def labels =…
-
JIRA Cloud does not limit access, it's your networking that's doing it on both Cloud and Server. You'll need to give this to your network admins - https://confluence.atlassian.com/cloud/atlassian-cloud-ip-ranges-and-domains-744721662.html
-
You'll need to hack the core code of the comments system to do that. It is just a language thing though - the phrase is held in a file which contains wording for all languages, so if you edit the contents of that, it's only a minor change.
-
Ah, I see. No, there's no way to do this, because the fields you need are *request* fields, and you are not raising requests this way. Requests are the interface between JIRA issues and the customers - you need to raise requests if you want to include the customers.
-
Ah, I see, you have written test cases in one format, and want to convert them into Zephyr cases. I think you should have a look at the Zephyr importer functions - they have ways of importing test steps, but you may need to convert your "feature files" into a standard format for them.
-
In what context do you want to "extract" this information, and what exactly is the information you need? For example, are you trying to write a macro that when you put it on a page, it will display an AD group and its attributes from the directory? Or you are writing a plugin to show more detail about a user in a profile…
-
You can attach files to JIRA issues, but I'm not sure that covers all of your question. Could you explain a little more about what you want from these files?
-
Just to clarify - are you saying that the layout of the characters in the title is poor? (It looks like they are not spaced out well to me). Or is the title wrong, it should be something else?
-
Atlassian admit that they don't know what this problem is. But there is at least an attempt at a fix - start at https://confluence.atlassian.com/confkb/confluence-fails-with-ora-01555-error-300812340.html