Comments
-
That's where my suggestion falls down - you can't hide issue types from the portal (without code, which you can't do on Cloud)
-
Not unless you set up some way to trap the route by which an issue was created. JIRA doesn't care if an issue was raised via the GUI, REST, Email, etc, it just logs the issue and does not distinguish between methods of creation. So you'd need to do something to catch it. Your requirement is a little harder than just…
-
You're not reporting the right Cloud version there, but the version of Cloud is not that important because it's always "latest" - Atlassian upgrade it frequently. You can always assume that Cloud is ahead of the latest Server version. The latest server version is 7.2, so the bug you're looking at was closed a long time…
-
No. Jira uses sequential numbering, end of story. If you were immensely careful, you could line the numbers up by not allowing creation of issues in a project by any means other than the external system, but that system would have to be sequential, and guarantee that every issue is duplicated perfectly. Most people deal…
-
Then I'm afraid you are wasting your time here, sorry. This is an Atlassian forum, and Sharepoint is a Microsoft product. You might be better off asking in Sharepoint related forums.
-
I'm not sure what you mean by "nintex", and you have not mentioned which Atlassian product you are having this problem with. It could be confluence, as many people try to use it to replace sharepoint, but you mention workflows, so it sounds like Jira. Either way, we need more information about what you've got configured in…
-
Yes, but you need to amend your permission schemes to do it. You want to add this group to "can log in" global permission, and then add them into your projects in such a way as they only get "browse project" and "vote" permissions. I would create a new global role called something like "read only", amend the permission…
-
Um, the question doesn't make a lot of sense. There is no "life cycle" of an issue in Java. Jira has a workflow engine in it that allows the end user to implement whatever process they need (obviously, there are limitations, gotchas etc). There's a default workflow and an editor in Jira. There is java code for handling the…
-
Yup, rather than trying to hit the field itself, you need to go after the data it's deriving the information from! The source code is public though - I've built a couple of simple variations on the participants field to make it use different rules. For example adding "user has logged work on issue", "user has been an…
-
The "participants" custom field I *think* you are asking about is the one from the Jira Toolkit? If so, then this behaviour is correct. The participants field takes the * current assignee, * reporter, * anyone who has made a comment on the issue, adds them into a deduplicated list and puts that on screen for you So, your…
-
I'm sorry, this doesn't actually appear to have anything to do with JIRA now. The "pages" appear to be web pages in a different application, I can't see what its relationship to JIRA is
-
You say "one of the pages" - what is this page? How are the links being written on the page? For example, as you say it's JIRA, are the links actual web links in the links section, or text in a text field, or a url field, or text in a comment?
-
It's not a trivial requirement - Confluence has it built in and disabled because the load is spectacular. And the Cloud solution is not truly "enterprise" - it doesn't go above 1000 users for a start and can only store 25Gb data. For an Enterprise Confluence, you'll want your own Server install or even Data Centre (both of…
-
I'm afraid Cloud does not support the plugins you would need to be able to do this.
-
See previous comment.
-
Ah, my apologies, I've not had to deal with a client having memory issues with Java 8 yet, so I've not run into the term.If I understand it correctly, I'd say that's not a problem - it's supposed to dynamically re-allocate as it's required, so it should really be full all the time.
-
I think you need to explain what you mean by "metaspace", it's not a term I recognise when talking about Java memory settings.
-
Remove your developers "project administration" rights.
-
I'm afraid I understand that even less. Let me paraphrase what you just said back, so it's clear why I don't understand:You've got a new department who will use Confluence. You created "space B" for them to work in, and they've been happily adding things. Now you want to tidy it up, and store their work in "Space B". That…
-
I think we need a bit of context on that question. A space can have thousands of pages, so "converting" it into a single page probably isn't useful. Could you explain roughly why you think you want to do this?
-
No, there is no "waste basket" function in Jira - delete is immediate.
-
You will need to restore it from a backup - if an issue or attachment is deleted from Jira, it is gone, completely.
-
If it's an OnDemand trial, then you can't install plugins. https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Plugin+Policy If it's a standalone trial, then yes, you can.
-
There's no way to remove spaces from the indices, because the internals of Confluence relies on the index to provide a lot of functions. It's not just search. If you did stop indexing your Sandbox space, it would become utterly useless as half your macros and most of the navigation would stop working. You'd end up with a…
-
Have you tried the issue collector?
-
It's quite likely that the workflow in the project is preventing some of the movement - you'll need to look at the workflows to establish what transitions are protected by what conditions. "Be the assignee" is one of them, but it's quite likely that you'll find others like "must be in the developers role" or "must be in…
-
Yes, the certs stuff can be "fun" ;-) I'm not entirely sure what the firewall vendor was, but I do know they had a set of dedicated Linux boxes that we had to tell Crowd to talk to. I don't think it was anything more complex than a username/password challenge, then the firewall would pass traffic from that source.
-
My clients have used: * Apache, SSL and certificates. The systems are on the raw internet, but you can't get past Apache without a valid certificate * Crowd for ID management, integrated with their firewall * VPNs to drill through corporate firewalls, so the systems aren't really on the internet, but people can use the…
-
You are right that only one "Issue type screen scheme" can be associated with a project, but that is easy to confuse with a "Screen scheme". The "issue type screen scheme" is a collection of "screen schemes" - it says "in this project, use screen scheme 1 for issue types A, B and C, screen scheme 2 for D and E, and screen…
-
No, I'm referring to you pulling out the internal backup process and rewriting it to enable theses exclusions But yes, you could try writing your own backup system using the CLI or plugins though.