Comments
-
It could be all sorts of things, but it's usually an environment setting that's causing the use of the wrong version of Java or other classes. Check the logs to see what version is running, where from and what the full error message is.
-
You'll need to hack the code in Confluence that handles it all, it's not a configurable option.
-
There's three key things you need to consider here, and one very important concept. Resolution and Status are totally independent 1. Resolution is a flag - when empty, JIRA considers the issue as needing attention. When it is set to any value, it strikes out the issue key, and considers it "resolved" 2. Status is an…
-
"Sub workflows" are a nonsense you've probably picked up from some legacy software that does it wrong. A workflow should represent your process for an item in full. You should always be able to point at an item and say "this item is at that point in the workflow". You can, of course group these together, and that's what…
-
Looks like a duplicate of https://community.atlassian.com/t5/JIRA-Software-questions/After-Implementation-of-SSL-on-JIRA-version-7-0-10-we-got-Error/qaq-p/578100/comment-id/11301#M11301 which has more information and a start on an answer.
-
I suspect the system can't talk to itself over REST because of something not right in the SSL configuration, but if that's the case, I would expect other errors as well as this one. You should read the log file to find out what the internal error is.
-
Duplicate of the (answered) https://community.atlassian.com/t5/JIRA-Core-discussions/Could-not-find-quot-com-atlassian-jira-web-action-project/td-p/578113
-
You need some code that can pick up the change to the current issue and issue automatic transitions on the others. You could write it for yourself, but there are add-ons in the marketplace that already do "transition linked issue(s)", so I'd strongly recommend a look at those before starting on your own.
-
You will need a little bit of code to do this. You should be able to do it in a "user macro" though and I'd use the one in the library - sample code is at https://confluence.atlassian.com/disc/shared-user-macros/count-pages-in-space (may need adjusting for later versions of confluence, but you'll get the idea)
-
Ouch, that sounds like one of those times when something goes bang in the middle of an update and there's nothing you can do (the apocryphal story about the cleaner pulling out the plug so they can run the hoover, just as one of your users clicked on an issue edit) I usually avoid it, but I think you may want to update the…
-
* Centos is one of the operating systems near, if not at, the top of the list for running Confluence on, and the first one most of us reach for when given a free choice! * Confluence is a server, it needs no GUI on the server. The client is (usually) a browser on another computer. The basic install runs on a command line,…
-
Is bug a sub-task type? Sub-tasks don't appear in the backlog because they don't have any use in there.
-
No, that's hacking core code, which you can't do at all on Cloud installations
-
That sounds wrong, although there is a hard way to do it in the workflow. I think you need to replicate the behaviour to confirm it, then look at the properties on each status where the sub-task controls are not there.
-
>Currently when a user is a project admin they do not have access to create/rename custom fields, edit/create issue types or screens, etc Correct, these are admin level actions as the objects you'd be working on are global and shared. Atlassian are working on devolving this more (7.3 grants project admins limited access to…
-
A board is a view of a set of issues. To include the issues from other boards, you need a merged copy of their filters to pull in both of them. You say you've already tried that, but I suspect there's an error or misunderstanding in it when you've said "it doesn't show the issues assigned to us". I think we need to see…
-
Comments belong to issues, there's no separation of who is leaving comments for whom.
-
See the original answer.
-
How would a system know that a user intends to create a task until the user actually does? Monitoring others is easy in JIRA though, you can set up notifications to send emails when issues are created, and simply ask "who created issues" and it'll tell you when it was done and give you any or all of the rest of the data on…
-
That doesn't make a lot of sense to me. Code doesn't usually get stored in JIRA, but even if it is, then all you need to do is not let the theives in. I'm not sure that there's any "add-on" that will do anything different from the core functions.
-
You will need coding to do this, as "create issue" permission really is for create in a project. It's not limited by issue type. There are some tricks you can play with javascript, and maybe fields that block things, but these are ugly for your users and usually easy to bypass.
-
>Any possible solution so that even if the users have Work on Issues permission, they will not be able to log work? No, because you have given them work on permission.
-
Your quick filter specifically excludes sub-task 1. That's what you have built it to do. You will need to create a quick-filter that includes the other sub-task instead of dropping it.
-
There are some options around, but it is hard to keep up with the pace of Atlassian development sometimes. The only system I am aware of is one that my colleagues have developed, and open-sourced. The blog at http://labs.adaptavist.com/labs/2015/12/24/christmas-present-opensource/ is a brief introduction, and the stuff you…
-
Possibly, but you need to define what you expect "Data loss prevention" to do.
-
Still no emails from the site.
-
Did you try the xml fix documented in that bug?
-
Yes, in the admin interface, they can see that the board exists, as they may need to administrate it. They do not get access to use it unless the permissions for it explicitly inclues them though. Just because they're an admin doesn't mean they should see a board when they're using the system as though they're a standard…
-
You need to get your admins to make sure you either have admin permission or are in one of the groups that has "space create" rights in the global permissions.
-
It's a little more complex than that. You need to look at two things. First, there is the "permission scheme". This is a set of rules that says who in your system can do what with a project. It does not usually refer directly to individuals or groups (it can, but we strongly recommend that you do not do that). It usually…