Comments
-
Yeah. Still don't. While it's a good add-on for what it does, please, just step away from the database, it's the single worst way of looking at Jira data.
-
Ugh, no, you don't want multiple reporters on a single issue. CC fields and watchers are the way to include other people.
-
Actually, no. The last version of Community (called Answers) was Confluence Questions. This platform is "Lithium" Lithium doesn't have much integration with the Atlassian products. If your users are working in Jira and Confluence, I'd strongly recommend continuing there and looking at adding Questions and maybe service…
-
You'll need premier support - see https://www.atlassian.com/enterprise/support-services for the options
-
As Sap said, via an add-on - JMWE has this if I remember right, but there are others that can do it.
-
Start with a look through https://confluence.atlassian.com/jirakb/several-actions-such-as-issue-ranking-move-export-are-failing-779159169.html
-
You could add a new custom field for CC, or change the permissions to allow you to add "watchers" to it.
-
The problem is not "errors" in the add-on, but "errors in what you're doing". Text fields are not suitable for gathering together like this because they are text. The add-on is having to do a vast amount of work to build a false equivalence and find the odd potentially matching blocks of text over a range of data that is…
-
I'm afraid there's no image. If you want to "edit" content though, on a create screen, you just click on the field you want to put data in.
-
Edit the workflow, and delete the transition.
-
What type of fields are the two columns?
-
Yes, that's the one I have had to remove from several Jira installations to fix their performance issues.
-
You'll need an App to provide test cases and so-on. See https://marketplace.atlassian.com/search?product=jira&query=test%20management to get the list of options to try. (I would normally recommend on, but my company makes one of them, so it would look biased)
-
Yep. Another reason why it's pointless - you can play some tricks, but it's not really worth trying to pass through. By all means, set up the cname, but point it at a web-page that simple redirects to the portal.
-
It's a bit fuzzier now. Atlassian have admitted that JaC (the public issue tracker) is basically a skip on fire - it's hard to work with the sheer volume of stuff in there and they're increasingly looking here for the more high level guidance. So, while JaC has a number of issues related to this, I'm not sure they're much…
-
This usually means that Synchrony is not reachable by Confluence. Sometimes, it's offline, but you've checked that. Next thing I'd look at is routing - from the Confluence server, try telnet <synchrony server> 8091 and see if it responds. Note - even though Synchrony is almost certainly on the Confluence server (it doesn't…
-
This is what it says - the field "resolution" is not on the edit screen, so you can't change it. The obvious answer is "add it to the edit screen", but in reality DO NOT DO THIS. If you do, your users will set a resolution, hence closing every issue, on every edit. You should only put resolution on transition screens -…
-
Jira does not have a function to downgrade the options by group for reports.
-
I'd probably start with the third business project - that's got a slightly more complex workflow than most (6 status rather than 3 or 4), so when you're editing the workflow, you've got more to update, rather than adding lots. For the fields, it doesn't matter what template you use, you're going to need to add all of them.
-
The issue navigator will show sub tasks if they are included by the current filter. Basic or advanced.
-
I suspect what you mean is "restrictions created by a user who has now left". Problem is restrictions do not belong to users, they are applied to pages. Confluence does not care (or record) who put a restriction in place, just that there is one. Removing a user will have no effect on the restrictions, but it does leave you…
-
You said you wanted it "in the first screen", which is create. We can't help you if you can't tell us where in the process you want to use the time-tracking.
-
This is only a partial "fix". If people use the cname instead of the actual location, they will get errors on dashboards and some reports and displays. These will not be too bad though, they will go away as when they start following links and menu options, they will be pushed on to the real url
-
No, we're not talking about that (and that isn't a problem anyway), it's the "can't add transition in draft unless there's one there already" problem.
-
To answer the question literally: Rewrite Jira and add the code required to do permissions at lower levels. Jira permissions are done only at a project level. There's nothing to cascade down to. You can do a little bit with issue security, but that only applies with "view", not the other 25ish permissions. To do what you…
-
The issue view is broken up into a set of panels. You cannot re-arrange these panels, or choose what appears in them. The way to think of what it does is: Take the list of fields for the "view" screen you have defined and for each one, choose a place for it defined by type * Date and time fields are put in the dates panel…
-
See the accepted answers.
-
Yes, you might find Questions for Confluence is what you're looking for. However, it's not seen a lot of love from Atlassian recently in my opinion - it works, but has seen little in the way of new features. Feels like they're happy with what it does and don't have any big ideas for improvements.
-
Ok, my apologies, I was not clear. * There are three Jira applications - Core, Service Desk and Software. * Core is a platform as well as an issue tracker. Service Desk and Software are applications for that platform. * So, if you want a well integrated set of the three, you should install Core, then add Service Desk and…
-
Ok, but that looks right to me. If a new user was created by the import, then the have not "had their access removed", they never had any in the first place.