Comments
-
Contact the addon author for an update. In the meantime, your options are * Wait * Don't upgrade to JIRA 6.3 until a release is done * Look at replacing it with other stuff * If you're desperate, you could risk installing the latest version and hoping it does no damage and works as well, but I wouldn't recommend it without…
-
If the servers are behaving to the IMAP/POP3/SMTP standards, then they should be fine. I can't help you with "several problems, it did not work" without knowing what you set up and how. (One quick and dirty test though - from your machine, or better, the JIRA machine, try a simple "telnet mailserver 25" - if the smtp…
-
It supports standard setups for POP3 and IMAP for incoming mail, and SMTP for sending. However, I'm not sure that office 365 runs them as per standard, as I've heard people are unable to connect because it's broken and only implements the rather poor MAPI protocol
-
But accurate.
-
It's basically anyone who can log in. But there are three JIRA applications and it gets a bit complex. JIRA Core users count towards your Core licence JIRA Software users count towards your Software licence. They also get Core access, but that does not count towards your Core licence, it's part of the Software Licence.…
-
I'd use the banner to put something in big red letters across the top - something like "you will lose everything you put in here" But yes, this is a case where it would be useful to have the "turn off" access. You could remove the jira-users group from the global "can use" permission - I think that should lock everyone…
-
You don't. On Cloud, you're not able to do the things that usually require users to be locked out while they are done (upgrades and migrations etc). So there's no need for it.
-
It's the other way around - will the Zephyr plugin version 3.2 have been written to work on JIRA 7.2.6? I'm not 100% sure we're looking at the same add-on, but the list of Zephyr add-on versions I found says it is - see https://marketplace.atlassian.com/plugins/com.thed.zephyr.je/versions
-
What are you doing to "park" a project?
-
Atlassian will give you an export of your data and attachments that you can use to populate your own system.
-
Does the pre-existing board's filter include the new project yet?
-
Boards don't belong to projects, and projects don't belong to boards. A board is a view of a set of issues which may select issues from your project. If it does, then JIRA will show you that there is a relationship there, but it's via the issues. So, yes, you can get your board to pick up issues from your project. Go to…
-
Yes, I've noticed that, there's a slightly clumsy work-around. Change the name to something it won't get confused with, like "Ready for Test (temp)", then again to "Ready for Test"
-
That's not a Script Runner or JIRA error. The email address you are sending the mail to is not known to the email server it is going to. It's not a valid address.
-
You didn't mention that before. That'll go back to the "you'll need to write" bit, because you will need to do some coding. The document you've found is about customising the outgoing emails, but your partial specification suggests you want to be looking at incoming email, which needs an email handler - see…
-
That look like half of a statement of a requirement - could you give us full context? (Although, I suspect the answer is "you'll need to write your own email handler to parse incoming emails for the field, or find one that can do it for you, such as JEMH")
-
Ooops! Happens to all of us, I still do that regularly. :-)
-
I think Daniel was asking about the type of custom field, not the renderer - is it short text, unlimited text or something else?
-
You can't. Any add-on will provide a set of functions that could be used anywhere. Some may be limited to projects, some are identifiable by saved data (a custom field will, well, exist on the list. A post-function will be referred to in workflows, etc) But there's no way of knowing where something like the CLI connector…
-
The two fields are separate, and enabled separately in each project. Because of that, it can't show you one of the fields because it's only in the other project. I would do two things: * To get around the initial problem, switch to advanced search and use "(project in (a, b, c) and 'work order' = x) or (project in d, e, f…
-
How are you putting this "work order or work order project" information into JIRA?
-
No. JIRA doesn't have that type of heirarchy. All projects are equal. You could try the Structure add-on if you want something more complex than Category, Project, Issue, Sub-task. But I'd take a look at Portfolio - it doesn't really do what you describe here, but it does offer functionality which helps you work as though…
-
Is your mail server configured correctly? You need it to have either POP3 or IMAP support. The errors you are getting imply that it is not configured correctly for either of them.
-
Assuming you used the whole system backup, then you can use "project import" to restore it. See https://confluence.atlassian.com/jira/restoring-a-project-from-backup-185729444.html
-
I'm afraid just telling us that it doesn't work is not useful. We don't know what you're doing, so we can't tell you how to correct or improve it.
-
Save the spreadsheet as CSV and use the CSV importer
-
You don't get access to log files on Cloud. However, for this case, they wouldn't tell you anything anyway. Applicatioon logs are for telling you what the code is doing, and access logs are for what pages are hit by whom, they're not for tracking application data activity. Status isn't really a "field", it's an indicator…
-
No, you need a 250 user licences to match your JIRA licence. In the future, that may change if Portfolio makes the transition from "add-on" to "application" like JIRA Software and Service Desk have, but I don't know if that's even a plan for Portfolio.
-
To buy a licence, you need to set up a https://my.atlassian.com/ account and purchase it through that. Could you explain where you are stuck in that process?
-
I don't think this is a bug, I think you've set up the link incorrectly. Take a look at the link settings in the admin settings for it.