Comments
-
Ok, looks like Marvelution have reorganisedtheir Confluence space and not updated the marketplace entry (well, mostly dropped it, at least from public view). Definitely needs to go to them.
-
I'm afraid we're on the JIRA end of it, not Jenkins - you'll need to get in touch with the authors of the add-on. Could you tell us which page you're looking for though, we may be able to find something for you.
-
That is often file ownership and/or permissions - make sure the user that the JIRA service is running as has full access to the files in there.
-
Find or write an add-on is your best option, although I don't know of any. If not, then try the REST api for talking to JIRA - I worked with Buildforge before it was bought by IBM and was able to do some SOAP stuff with it off-the-shelf, so I can't imagine REST would be any different.
-
Not in the UI. You can edit the .vm files that generate the field areas to increase their width, but they are by *type*, so a change for one type affects all of them (e.g. you edit select-view.vm to increase the width of a select lists, all the custom fields that are select lists will be wider). You can start adding code…
-
It's not. If you can edit an issue, you can edit it. Jira doesn't do field level security. You could do it with the Quisapps field security plugin, or botch in some javascript (seriously, not advised), but Jira doesn't do it natively. Or, you could move the edit into transitions and control them. Remove the components…
-
Somehow, the other projects are configured to allow that developer "browse" rights. First, look at the developer's profile, and note what groups they are in. Secondly, go to the project that they should not be seeing and read it's permission scheme for the BROWSE line. Check that against the developers roles and groups,…
-
Ok, if you'd said that when I asked, I'd have been able to help faster. I'd agree that the docs are not 100% clear here, in that they lead you to a new installation of not-latest, rather than an upgrade, and that page doesn't really highlight what you need to do here. The reason your downloads are not usable is that you…
-
Without knowing what you're trying to accomplish, I can't even validate that you're looking at the right document, let alone the rest of it.
-
You still have not explained what you are doing. Quoting bits of the docs at us does not answer that question. That section startes with "sometimes". Define what those "sometimes" are. "I already tried all types" still does not tell us what you are doing or why. What are you trying to do? Why are you asking about the type…
-
That tells us precisely nothing about what you are trying to do with a download. Please tell us what you are trying to do here?
-
Depends on what you're doing with it.
-
Your code needs to perform REST calls, we can't help you with that, as you could be doing anything. But the calls it needs to make to JIRA are pretty standard. Start at https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis to get a feel for them.
-
JIRA keeps records of users because it needs them for the history reporting. Deleting it from LDAP is fine, as it keeps a local copy, but it keeps it in a "this user has gone" state, which is why you can't use the old user.
-
Use "create space". I think you need to have a read of https://confluence.atlassian.com/display/DOC/Getting+Started+as+Confluence+Administrator
-
With an admin account, click create space.
-
Not really. Workflows tend to be either very standard, or built to fit a process for a specific set of users. But, check out the workflow bundles in the marketplace.
-
No. There is no selection on that first list, you choose one option, and the second box repopulates with the sub-list. If you want only one option in the first list, change the option list so that there is only one.
-
I don't think I quite understand the question. With a cascading select, you select one option in the first list and that changes the available selection for the second list. You only choose one option in the second list (which could be none) and all the possible combinations are unique, so you're only ever choosing a…
-
Which pages are you looking at? Most of the cloud/latest stuff seems ok to me
-
Go to the JIRA site and enter your user id and password into the login prompts. I have a feeling we're missing something here - you've not explained why you cannot get in that way.
-
The export contains all your data. I'm not aware of any option to suspend an account, you'd need to talk to sales. But I suspect you'll need to take your backup, keep it safe, and then import it into a new OnDemand when you do take up the option again.
-
Ah, and now we see another reason for not allowing large attachments (there are good reasons the limit is set quite low by default) I suspect the only way you can fix this is to replace the document in the database with a much smaller one, so that it can then delete it properly.
-
Most of us don't have dual accounts - we log in as a user who is in the jira-users group, and also in the admin groups. When we need to do admin work, we hit the admin menus and JIRA will then do a "websudo" prompt for further authorisation. Your right to do system admin has no effect or interaction with the issues or…
-
As I said in my answer, you need to ensure that the existing reporter has "create issue" in the target project when you do the move.
-
I suspect the old reporter does not have "create issue" rights in the target project. In other words, they are no longer a valid option for the reporter field, so Jira takes the current user as the reporter instead.
-
Nope, this is pretty common - the default permissions don't work for people who want "can only see a few spaces" I'm sorry, but you need to un-pick the defaults and rebuild them. Two basic approaches: 1. Remove "confluence users" from every permission and space, replacing it with smaller and/or more dedicated groups or the…
-
No, that's a dynamic request and not a "group". A group is a list of users grouped together, not a list of currently active users. The applications using Seraph are also flexible - they allow you do explicitly nominate groups as "can log in", so you actually need to ask the application, not just Seraph. (Also, "currently…
-
Just to be clear, you are asking about Project level custom fields? Not Issue level fields? You can use the project description area to show simple information like that, but there are no project level fields really.
-
Jira doesn't do this. Create permissions are done by project, not issue-type There are some basic workarounds - you can use javascript or the behaviours plugin to chop down the issues available list (easily bypassed of course, and ignored by REST and other processes), and there's an absolute block trick (you put a field…