Comments
-
If you stop paying the bill, your Cloud system will be shut down, and eventually deleted, although your owner account will be warned about this, it's not a lot of good to you. My guess is that your old boss sent the email to completely the wrong place. What he needed to do was raise a support request. Or better, he should…
-
What events are being fired by the workflow transitions?
-
Yes, two fields mean two filter options, and some things go wrong if you use the same name for two different fields. I add a simple . to the name of one of one of them, or use capitals to distinguish them >Also JIRA doesn't allo to create Context based on Issue Types. It's possible only based on projects. Er, yes it does -…
-
I'm really really sorry, I've messed up. Confluence doesn't have roles. When you started talking about tasks, my brain went wrong and slipped into JIRA thinking, and my last comment is completely wrong.I'm afraid you'll need to go through all of your spaces and make sure that there is a group granted "view" permissions for…
-
Yes, although it would be better to use a role, and put the group into that (i.e. have a role like "viewer" defined globally, put the rule "Browse = role (viewer)" into the permission scheme, and then put your users and/or groups into the role of viewer in that project. That lets you have more control over each project…
-
Is there actually any more question here? Or does "read access for all" solve the problem?
-
What do you want from this "communication"? Would it be worth granting read access to most/all of your spaces for all users?
-
I'm not sure why it doesn't search, but try putting in your login ID instead of your name. The problem isn't that you can't change it, but that it doesn't know which user you want.
-
Done Yes, I'd create a workflow that only has one status and no resolution field on offer.
-
just don't have a Resolution set for those issues that you always want to see when you select that project
-
So you're not really using the workflow at all. So there's no point in resolving them.
-
But if something is actively tracked, why has it been resolved? You'd normally only end a record after it no longer needs tracking. The whole point of the workflow is that issues eventually get solved or go away, so there's an end point at which time the item is "resolved". If you don't need to do that, what's the benefit…
-
The filter default is hard-coded, presumably because Atlassian have found the most sensible thing to do is go along with the standard assumption - resolved issues don't need any action, and therefore don't need to clutter up default displays.
-
I think there's a problem with the idea, and a good reason for the design. Closed issues are done with, so most people don't need to see them in a summary.
-
Click delete in the issue actions menu (the ... towards the top right) However, delete issue is very final (as in, delete the wrong thing and you will need to restore backups by hand) so most places restrict it to a small group of trusted users, or disable it completely. Have a look at the project's permissions, they give…
-
Nope, not in the off-the-shelf Confluence But the "multi excerpt" add-on does the job well.
-
Ok, I'm stuck, I'm afraid you're going to need to give us a screenshot of the group list where you've added the groups, and then an example of the dropdown missing the groups.
-
Ok (I read stuff too fast sometimes too, I know exactly what you mean)So, if I understand this, you're going into a permission scheme, and clicking "add" next to one of the lines, and landing on the permission add screen. In there, you've got the list of permissions you might want to add and you've selected one or more of…
-
No, sorry, not "why", I'm asking *where* you are doing this in JIRA.
-
Where are you "permissioning projects to certain groups"?
-
It is possible with a bit of scripting, but it is strongly recommended that you don't upgrades without reading the release notes. You can (and will) find behaviour changes that you weren't expecting and there could even be data loss.
-
The rule for consuming a licence is "the user can log in", not "is a user". Administrators can always log in, so they count towards the licence. Even if they're not in the user group. The documentation used to be clear on this, but it seems that an edit has made it unclear at some point.
-
Yes and no. You can tell Tomcat/Jira to place the logs anywhere you want to on the local server. In several places, I've mounted remote or shared directories on the servers and the applications quite happily write the logs to them. Replication is a different matter - there's nothing in the applications to do this. But…
-
This looks like it's been posted out-of-context - could you point us to the original discussion?
-
No, if your directory allows them to edit their email, then, they can.
-
Depends on your logging levels. I suspect it's not detailed enough by default, but I'm not sure. Try https://confluence.atlassian.com/display/JIRAKB/Notifications+Troubleshootingand https://confluence.atlassian.com/display/JIRA/Logging+and+Profilingto change log levels
-
Because you've put in a broken email address for the user you are sending it to
-
Yup, sounds like you don't have access to the projects. Remember Admin rights give you access to admin functions, not everything automatically (because that's a terrible access model), so if you want to see a project as a user, you need to make sure you give yourself permissions
-
The REST API for 4.3 and 7.0 is very different, even the urls are not the same. Try coding for the urls and calls over at https://docs.atlassian.com/jira/REST/4.3/
-
When Gabrielle mentions "is the issue done" - could you check that the issue is in the "done" column on the working view of the board?