Comments
-
Ok, that means they can't be edited. You need to add them to the edit screen to enable them to be changed.
-
Do you have them when you click "edit" at the top left of the issue? (next to the actions and transitions/workflow)
-
If you go over your licence limit, then JIRA will restrict functionality until you get back down below the limit. Your users will be able to log in and browse, but not create new issues (or projects)
-
Not really. It's in your backups, but the data that comprises a dashboard is gone from the database when a user clicks delete. All the filters etc are ok, but the dashboard config has gone.
-
It does, but there are plenty of places where only the name is shown to the user, so there would still be a problem there.
-
I suspect it's because it's confusing for users to see lists containing projects with the same name. If they're confronted with three prod-1-common, how do they know which one to select?
-
The page you've linked to is the starting point. We can't really tell you a lot more, without information about what wiki you want to import from or where you are stuck in the process.
-
The zip file you are trying to restore from is either too large, or it's damaged. Could you try unzipping it in an archiving application (e.g. unzip on a unix box) and check it is not damaged? Also, could you read the Confluence log to see if there are any other errors around the unzip?
-
You'll need some code to implement this, but if you've got the Scriptrunner addon, that would let you put in a very simple validator on the "create" transition.
-
JIRA doesn't expose the hooks you need to be able to do "edit validation". Script runner does though - https://jamieechlin.atlassian.net/wiki/display/GRV/Edit+Validators Be aware that it is only a partial implementation though - because JIRA doesn't have the internal structure for edit validation, there are places where…
-
It used to be valid. I think what's happened is no-one used the plugin so Pablo discontinued work on it and then did not renew ownership of the site. Subsequently, it's been taken up by a spammer.
-
It's worth thinking about a pre-commit hook in Subversion which scans for an issue-key and stops commit if there isn't one.
-
There's no support for external users on Cloud - the best Okta can do is store the user credentials and log in for them. But, you'll still need the list of users to help build the Okta side and I don't think there's an easy way to get a list.
-
Write a validator to scan the text entered and return "fail" if the string is missing. Start at https://confluence.atlassian.com/display/JIRA/Configuring+Workflow You could also try it in javascript (with the caveat that it's easy for people to bypass that)
-
No, my emails on followed questions have stopped arriving, so I've no way to see if people follow up, other than guess. From memory, you need an issuelinkmanager object, then you can go issueLinkManager.getIssueLinks(<issue>).size()
-
Well, it depends on what plugin you're using for scripting. But I've never done it myself, I wrote a field that counted links years ago, and then used a "number > x" validator on it.
-
Yes, that's because the field is not really a field - it's an area for the user to enter text that will be converted to issue links, not actual data to be checked. I'm afraid the JMWE isn't quite clever enough to validate this "field" - you'll need to find/write something that looks directly at the actual issue links to do…
-
I think you'd need to write a Confluence "theme" to do that - you need some css at a moderately high level to alter Confluence's basic layouts. (If you have a look at some Confluence themes, you can see stuff like the Documentation one giving you a panel and a page, and others do single columns). I'd be tempted to have a…
-
"In what system and where" is exactly what it says. What system are you doing this in? Where is the code being run? Your previous answer actually answers those questions fine.
-
Ah, you missed the point I made about REST. The reason you can't find a JSON format is that there is no function to do this. Unless I have missed it in that page.
-
In what system and where? I'm taking a guess that the target is Jira, but where are you trying to do this? As you're saying JSON, I'm guessing REST, in which case, you can't because it's not available yet (unless I've misunderstood https://docs.atlassian.com/jira/REST/latest/ ). But I'm really not sure, because there's not…
-
Same here - you can forbid someone from seeing an entire page (or tree of pages), but if they can see a page, they can save a copy, print it, and all the other functions you can do with a downloaded file (because that's what it is)
-
You closed it, so no-one was interested... No idea about the first one, there's no information on it. Second one - have you tried Valiantys?
-
Yes, but Agile and Service Desk are now "applications", so the licences are sort of merged if you want to compare them with the old models. You'd actually want to buy "JIRA Service Desk for 10 Agents", which will handle the "JIRA Core" bit for you.And yes, there's email interaction. I've not played with it a lot (my recent…
-
In Service Desk 1, you had to have JIRA licences for customers, but that was quite a while ago. Service Desk 2 and 3 follow a more appropriate model: You have three types of user: * JIRA users - people who will be using JIRA's functionality * Agents - people who will be using Service Desk as Agents (they also need to be…
-
What Operating System is the server on? Actually, I can't really give you much on this. I'm only familiar with logrotate on Unix machines for a start, so I'd refer you to google if you're on Windows. For logrotate on Unix, there's loads of documentation for it on the web too, much better written than anything I'd write for…
-
That's almost certainly a debug output in some code. Probably written into a plugin. If you use "system.out.println" then this is the sort of output you get. I'd start by looking at what plugins you have installed or updated on the day the crash happened. Use the plugin audit log to find any likely culprits. Also, in the…
-
I've heard of it, but it was only during an interview, where a candidate said she'd done migrations from systems to Jira or Rally. She told us it was a issue tracker, but I can't remember her opinion of it (obviously, the people she was working for had a lower opinion of it than they did of Jira or Rally)
-
Oooh, I was only talking to them about doing an OnDemand "as a product" before Christmas, so I know they're looking at this sort of thing. Virtual machine images were mentioned, alog with a "heck, stick it on a DVD, preconfigured - Atlassian-in-a-box". I hinted at a live server image (like whacking a Linux CD in a machine…
-
Because Atlassian Cloud support are not willing to support it, so it's disabled. See https://confluence.atlassian.com/display/Cloud/Restricted+Functions+in+Cloud+Applications for the list of things you can't do.