Comments
-
This won't work. The jira.issue.editable property is a workflow property. It kicks in on a workflow status. This means that if you did write a script that would set it to false when a custom field was X, all issues using that workflow would become uneditable while in the status you set it on as soon as you did it for the…
-
The best I've seen so far is the administration interface. A "complete structure" diagram would almost certainly be complex, hard to generate, harder to read, and actually not a lot of use in real life. As an admin, you generally don't care about the overall structure, you care about complexity, getting new config in…
-
Yes, you can still import. And report on the deactivated values. You just can't use the values when creating new issues with the "new issue" function, or editing them into place (imports are not considered "new" issues, they're thought of as "existing somewhere else and needing to be moved into your Jira")
-
I'm not that surprised - the non-space files could include all files that could be attached in the drafts across every space! I would not want to delete files from here in case people actually are planning to finish their drafts. But I would want to use something like your SQL to find out what all the drafts are and poke…
-
Go to the Atlassian account that got the original licence, find the licence you have (even if it's just evaluation) and add users to it. The user layers are tiered, so you're not adding X users, you're moving from X users up to Y users.
-
This does not appear to have anything to do with Atlassian applications (although they do use ofbiz in places, you should not be messing with any of their data unless it's via their UIs)
-
You have a post function (or possibly an automation or listener) setting the resolution to "done", after the user has chosen one.
-
It will do - other things the system is doing are being logged. You need to capture the chunk of application log that happens from just before you click until there's a related error appearing (it should be almost instant). Note - the logs you've posted look like they are application-server logs, not application logs.…
-
I would guess that you are using Jira Service Desk there, which has a totally different mail system, and doesn't use the keys at all. (Nor does it use the subject)
-
Ah, ok, you've edited the question to remove part of it, I wasn't sure why my answer no longer matched it! The last modification date of a page is derived from all the pages that make up its history, so it's not a simple SQL query - you have to go over the whole lot to see what the most recent change was. You might find it…
-
I'm not a "community liason" and it's not a rebuke. It was a comment that was trying to re-iterate a point that had been repeatedly ignored. Kanban boards are not 15 years old, and haven't been owned by Atlassian for anywhere near as long as that. They're not "barely functional" - millions of people are using them very…
-
Yes, sorry, Jira jargon - the issue Key is the project-sequence pair that humans see (your project-123), and the "id" is the numeric unique immutable issue-id in the database. The mail handlers that ship with Jira do not care what the subject line looks like beyond looking for the (first) issue key it finds in the subject.…
-
It is possible to rename Epic, but it's not a simple "rename". It's a massive pain and can cause some "interesting" problems, especially during upgrades and with add-ons. I can't recommend that you do it.
-
No, both of those are correct. The mail handlers are built to comment when they get an email with a key in the summary that they can match to an existing issue, and otherwise create a new issue. They're not built to de-duplicate because a lot of users don't need or want that, they rely purely on the issue key. If you want…
-
Epics in Software are built to function differently to other issue types. While Portfolio allows you to see other types as being at the same "level" as Epics, they do not become Epics and gain all their functions. Your goals remain standard issue types with no epic functions.
-
"Archived" emails are not removed in gmail, they're flagged and then hidden by the interface. Pop3 does not show that - as far as it's concerned, the emails are still in the inbox. You will need to delete them properly and then set up Jira. Note that if it didn't demand an empty mailbox, it would have to process and then…
-
Start with a look through https://confluence.atlassian.com/jirakb/mysql-communication-link-failure-214338032.html
-
In the log file, like there was before.
-
What has the error message changed to?
-
As the error message says, look at the 7th line and the error that says "empty array" - you can't get the first item when the array is empty. There is no custom field called customfield_10801. Try using the actual name of the field, not the id. Or use a call that tries to get the field by its id.
-
Well, you would, but an add-on will have to talk to Jira over the REST API, and that does not support it yet.
-
Then the mail server is choosing to reject it, although I'd expect a different error for that. Connection reset still almost certainly means "your network is not connecting"
-
No, that's wrong. Portfolio is an App that allows you to see and edit overarching plans across your Jira projects. It's not "view only" and it's not just for reading project data. Any user of Portfolio has to be a licenced user of Jira. But that's irrelevant - your Sales person needs to be a Jira user if you want him to…
-
You're right, Anne's answer is the most correct one, this one was incorrectly marked right. I've swapped them.
-
Not yet, and I suspect never - my guess is that classic software projects will be deprecated before roadmaps go into them.
-
I'm not able to find anything that can do this. It is possible in Server with a user macro (as you can get to the "information" page to look at the incoming link information)
-
I can't think of a way to do this. You could write a validator and/or condition that says "do not allow transition if there are too many attachments", but that would not block a user just adding too many attachments when they felt like it.
-
A user can't do it directly, admins are probably responsible for some of it. Nonspaced files broadly fall into two categories * Files that don't live in spaces - this is pretty much negligible, but includes things like the global site logo and graphical data from the odd add-on that doesn't belong in a space * Files that…
-
It is only available to Cloud users at the moment (and for the foreseeable - Atlassian have said they're not looking at bringing it to Server any time soon)
-
Actually, we don't know. None of what you've just described is standard Confluence functionality, so you'll need to explain the App or customisation that has been installed in order to do all of this. We're end-users of Atlassian stuff, we don't know your particular system!