Comments
-
Nope, I understand. Lack of flexibility like this is one of the weaknesses of Cloud.
-
You've found the wrong solution - that's about killing email off completely, and only on Server installations. For Cloud, you don't have the option to turn modules off, it's a restricted function (because you could cripple it and Atlassian Cloud support really don't want to have to fix that sort of mistake - in general,…
-
Ah, ok, well, if it's not there, then it's not enabled in OnDemand. I think you're stuck and you can't implement anything that will do what you're trying.
-
It's a listener, rather than a workflow item, but it's quite flexible, you can use it on one, some, or all transitions. Have a look through the doc for it - https://studio.plugins.atlassian.com/wiki/display/JTOOL/Auto+Transition+Listener
-
Off the shelf, you can't do it. You need code to read the incoming mail and perform the transition. Personally, I wouldn't write any, I'd simply try to get the JEMH installed, as that can do it (and has a raft of other immensely useful email functionality for Jira) However, you've said you're OnDemand, which means you…
-
It's there because comments are not a field, they're a conversation. They're offered to the user (if they have "comment" permission) because people often want to explain their changes, to stop those "why did you change component to something else" conversations. It's convenient and helpful for most and has the benefit of…
-
On Cloud, you don't. The base url should always be the url you access Confluence on. On Cloud servers, the base url is locked to the url of the service and hence there's no need for you to change the base url, because that would just break your site. The url for your service cannot (yet) be changed (I don't know if…
-
1. Possibly. Do you need the field to be used on the same project/issue type? That would be nonsense for single field, you absolutely have to have two fields, or there's no way to tell the two instances apart. However, if you want the field to have the same lists, same data, be mandatory on "bugs", but optional on "tasks",…
-
That's what I was about to post, it's the most I've seen about the relationships between tables. I'd also add that most of the relationships are logical rather than physical - the code handles them, not the database. Also, you might be better off asking Atlassian directly - I did get a good chunk of description once on a…
-
You don't. The licences they have are for their installation of JIRA Cloud. If you want to add them to yours, you need to get the extra licences for them.
-
You'll need the very latest version of Server you can download, and everything should come across ok. But read https://confluence.atlassian.com/adminjiracloud/migrating-from-jira-cloud-to-server-applications-776636236.html carefully before doing anything.
-
You need some scripting or code to do this. Unfortunately, they are not available on Cloud.
-
No. As the documentation says, the XML is effectively a copy of your database, and you need to back up the home directory and installation separately. Note that you need to think about the reasons for backups. A JIRA system can be rebuilt from just the XML and a copy of the attachments (although a database backup is…
-
Ok, it's able to create a backup at least, so yes, you can use that to move to a new server (any data added after the date/time on that file will be lost)See https://confluence.atlassian.com/display/JIRA/Migrating+JIRA+to+Another+Server
-
You need to fix the "bugged out" before you are going to get far with this. There is one option that could get you around it without needing access to a working JIRA, but it depends on how your current system is configured. What database are you using and is it on a separate server?
-
Code. You either need to write a "derived" custom field, or if it's for display on the issue only, you could probably do something with a message field (from the Jira toolkit) or a spot of javascript. However, as you're OnDemand, you can't install plugins, so I think you're pretty stuck
-
Not quite - export is "everything". Import allows you to read a full export and import bits of it (or do everything)
-
Projects, yes, you take an export file of everything, then use "import project". I am not sure that this is available in OnDemand, but I think it is. Fields, I'm not sure. If you mean the field configurations, then no, your only option is manual replication. If you just mean the data in the fields (the issue data) then…
-
This is more a network problem than Confluence. Your machine or network is blocking access on that ip/port. You'll need to find that block and remove it. It's probably your firewall - needs to be told to accept incoming tcp on that port.
-
You need an existing system administrator to add you to the group that has the "system administration" privilege (or do it in the external user directory if you're using one)
-
Ok, well, the custom field will do the job, but the section you're talking about is for the built-in "system fields". There's no way to add to those without hacking the core code in quite a lot of depth) The closest you can get is a custom field which you then move into the system field area. Again by hacking core code,…
-
What do you mean by "attribute"? What's wrong with a simple custom field to hold the data?
-
Running vast punts of searches against a database is a performance killer, so jira keeps a local and optimised and indexed chunk of data locally. This makes the whole system a lot faster. Rebuild index does what it says. Removes the current index and rebuild s a new one. In general, you can ignore it.
-
You probably need to comment on the original question and/or issue.
-
Ah, good, that's a sensible way to go.What's the size of the data? I'd be tempted to use bulk-edit, but that becomes cumbersome for several thousand issues.If it is large, then yes, I'd use the script runner to run and iterate over a filter for "demand priority is not empty" and update the system priority accordingly
-
What do you mean by "map"? I mean do you want to use JIRA priorities permanently? Copy the data? Display it differently? You can run whatever scripts you need to against one or many issue types, but I think you need to explain what the end goal is before we can help you much.
-
Ah, the joy of permissions. It's quite likely that you're using the off-the-shelf permissions, or permissions that are similar to them. Much as I understand why they're kept simple for defaults and new users, they really are a dreadful example of how to do permissions in Jira and I've been asking Atlassian to create a…
-
No idea. I suspect it's so simple, I've never looked for it! The users will look like any other user and you add them in the same way (then delete them from any can-log-in group, as Jira will add them to that automatically if you're using it's internal user management) To find out the can-log-in group, look in Admin ->…
-
Not explicitly, but you can certainly create a user who is not in the "can log in" group(s) and hence does not take up a license. All users have a single email address though, so you need to set it to a distribution list in your mail system for it.
-
All users with browse-project can see it on the project summary (I've got a feeling it comes out in some reports and there's a couple of places you can hover over the project name and get it in a tooltip as well)