Comments
-
This suggests you have a proxy which catches the external requests and takes the users to your server, but your internal network is routing directly to the server, and not proxying anything. Four options spring to mind. * Get your internal network to resolve to the proxy instead of the direct link, so the proxy can do its…
-
Two options: 1. Get the admins to change the project setup such that there's a role that gets notified on "create" events. Then put you in that role! 2. A subscription is available if you search for issues, save the filter and then click on "details" near the top. A subscription will email you a list of matching issues…
-
That looks odd, mine says stuff like: 2017-07-17 21:35:45,175 http-nio-2990-exec-9 anonymous 1295x47x2 z19bht 0:0:0:0:0:0:0:1 /rest/gadget/1.0/login login : 'nic' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie. 2017-07-17 21:35:45,227 http-nio-2990-exec-9 anonymous…
-
Confluence tracks all the updates internally. But some of us do use JIRA to track things like authorisation and archiving. Usually a simple link to the document in question, with some automation sometimes.
-
Unless you've deliberately turned off all the logging, it is definitely logging your attempts to log in. Have you checked the right log? And all the others in there?
-
The user or team name you have given the connector to work with the connection.
-
I don't think there's a way around that - you can't use it in a sprint because you don't have the permission to do so. That's a case for moving the issue into a project owned by the people who need to deal with it or possibly creating another issue (linked to the original) to track it in parallel
-
That's not healthy, but I don't think it's fatal, and I don't think it's anything to do with your users logging in. What do the logs say at the time someone tries to log in? Refusal to let a user in is recorded, with a reason.
-
An issue tracker is for tracking issues, not doing documentation management. I'm not sure there's much use for what you call a "basic feature" - it's very rare you see a 1:1 relationship between JIRA issues and Confluence pages. They don't even use the same naming schemes. Confluence pages are named, JIRA issues have a…
-
Ah, I see. You need to disable the activity feed to supress them. I'm not sure that can be done on a group basis, I think you can only turn the whole thing off
-
There's nothing wrong with your query except the "sprint" clause, which triggers it to be looked at as having a completely global context. You will find that you need sprint rights in all the projects, but your question shows that you've got that (when the sprint thing is removed) If the sprint thing is a critical part of…
-
You go on to the server and use the JIRA stop and start scripts to halt the whole service.
-
Could you explain what you mean by "able to see all the updates of pages from other spaces"? Do you mean they have access to other spaces?
-
What does the log say is wrong? (If it is refused logins, the best guess is that the user directory is failing for some reason, but that really is a guess, as your question has so little information in it)
-
Ok, this is a bit of an obscure one, but it's because of the use of the sprint field in the query. Sprints are not project or even board fields, they're global. When you introduce the sprint field into a filter, JIRA has to assume you mean "all projects" (even if another clause limits it, the field makes the search…
-
Boards do not belong to a project or contain issues. Boards are a view of a set of issues. If you want an issue to appear on one board and not another, you need to set the data on it so that the first board selects the issue and the second does not. I don't know if this will suit you, but it's an example of a way to do it.…
-
You can add your own issue types to a project in the usual way, you don't have to stick with the defaults. The best way to handle several customers is up to you, it should match the way you want to work. Sometimes you might want a project per customer, other times, your project is more for your team, so you'd create a…
-
Yes, you'll need two status with different descriptions. The main tip for workflows is to always consider the resolution. Think where you set it and clear it (And always set/clear it, even if you don't use the field) A second one is *always* provide at least one route out of a status. Even if you use a condition to say…
-
There are a number of "create sub-tasks" post-functions available in add-ons in the marketplace. You can use those on the "create issue" transition to create sub-tasks. For different issue types, you can simply have separate workflows associated with the issue types. A sub-task is automatically part of its parent when…
-
It sounds like there's some form of escaping or character problem with what Informatica is sending. I'd want to see exactly what it is trying to send, in order to de-bug it. Your last query is incorrect though, as there are no issues without a project. You just leave the query blank, and it will return all issues.
-
Something has changed if it stopped working, so you'll need to work out what did. Are you on Server or Cloud? Also, are you sure the emails are arriving in the mailbox they are supposed to, and do you know if JIRA is processing them? (It will delete them when it's tried to import them)
-
>Upon creating the issue, it should automatically link the ticket as sub-task You should be using sub-task types to do this. Then the link is automatic, because you create the issue as a sub-task of a parent.
-
It's usually the proxyName, proxyPort and scheme settings that are wrong, as they have to be added to make a proxy work with Atlassian applications.
-
No, you need to understand what I've said, not repeat the question. A status is *always* visible on an issue, so "user cannot see status" is nonsense. Do you mean that the *transitions* are missing? Or something else?
-
Yes, you could write something to do this. I don't know how hard it would be. Injecting the tray icon and display into the menu would be reasonably easy, but I don't know the best way to get stuff into it. A listener for "everything" feels like overkill. If it's just "my tasks get assigned to me" though, I'd simplify it…
-
Drag and drop them into the "done" column.
-
What do the logs say?
-
You'll need to go further if you're planning to use project import. From 4.4.5, you need to upgrade again to 5.2, then 6.4, then 7. Project import requires that the source and target systems are on the same version.
-
TAT? You don't want me to explain what that acronym means around here in public... There are a couple of reports in JIRA that do "time in status" and the marketplace is well worth a look, but I don't know what you mean by TAT, so I'm not sure I can point you at anything specific.
-
You can only extend it a few times, 3-5 I think It will stop working after you renew too many times, becoming read-only. You'll then need to buy a licence.