Comments
-
@Sivakumar Sokkalingam - you *must* rename that "unresolved" resolution on your list immediately, and probably "open" as well, it's making your data utter nonsense. As Joe says, you need the resolution field to be empty when an issue is not resolved. Resolutions named "open", "unresolved", "unfinished" and so on are wrong.…
-
Both - Confluence is for writing up anything you want, and works for internal and external users (At the same time - most of us have some external facing spaces and a load of internal ones. It also provides a neat self-help feature when used as a knowledge base for I don't know about atom - if you mean the text editor, it…
-
Yes, those usages are correct. The tools best used to work with JIRA and Bitbucket are probably not defined by them - you should use the tools that work best for you for your coding. Most IDEs (Idea, Eclipse, Netbeans etc) have integrations for JIRA and Bitbucket, so you are pretty free to use whatever one you like. Some…
-
You have to do it the hard way - read the workflow schemes to see if it is any of them, then read the projects to see if the workflow scheme is in use. I would take a different approach. Do some housekeeping, deleting all inactive workflow schemes and workflows from the "inactive" section in the UI. Then your existing SQL…
-
The documentation is absolutely right, but I don't think you're quite seeing the concept of a "container". Tomcat is an "application server", which can run many applications. It's usually referred to as a "container" when it does that. You should not do that with JIRA and Confluence, but, more importantly, you don't need…
-
Yeah, inheriting systems is great sometimes. But there's always the odd quirk, where someone hasn't documented it. (Not sure I'd say "legacy" though, as a large chunk of the work I do is moving people from legacy systems on to Atlassian stuff)
-
Bother, that rules out what I thought it was. Sorry, I'm stuck on this one. I thought it was simply "you can only share with the roles you belong to"
-
Are you in the role that is missing? And the one that should not be there?
-
You are over-thinking this. The fact your server is running JIRA is irrelevant. JIRA and Confluence are totally separate services. If I simplify your question down to the basics of what you need to ask, the answer is 1. Check the server has the resources needed to run JIRA and Confluence simultaneously 2. Install…
-
JQL won't do that, it's for getting a list of issues, not retreiving or reporting on their data. But, in the issue navigator, you can just search for "Date deployed to live is not empty order by date deployed to live desc" and it'll give you a list of issues, with the first one being the latest.
-
Apologies for misleading you with "set" instead of "update", I forget the exact words, and pick synonyms a little too often!
-
Confluence does not run properly on OpenJDK - use the java that comes with the Confluence installation. That doesn't affect the database drivers though. It still sounds like the credentials are wrong, or the user has no db access.
-
JIRA creates, or comments on, issues when it gets incoming email, and it uses the information in the mail to do so. So I'm not quite sure what you are asking for here?
-
Editing workflows is possible for project admins if the workflow in their project is not shared with any other project. JIRA 7.3+
-
Ann is right - upgrade it properly. Although, there is another option - install an empty Confluence, export the spaces you want to transfer over one at a time and then import them one at a time - the xml space exports are mostly version-agnostic.
-
I resorted to writing a report ages ago. It listed the projects with the most recently updated issue, date of oldest issue, ID (as that always increases when you create new projects, so you know the newest project is the highest number etc), and a couple of other bits related to it. I keep meaning to re-develop it (it was…
-
Postgres is definitely running, but with those settings, can you just confirm that it is on the same machine as Confluence? If it is, then the error message you are seeing is good - it says the right drivers are in place (although your apt-get is of zero use - it installs the drivers somewhere else. You'll have picked up…
-
It sounds like you have not considered the process flow in full, and have not added the transitions for "verification" or "close" to the workflow. If that is the case, then you will need to edit the workflow. If it is not that, then you'll need to explain more, as it's not clear what else it might be.
-
Duplicate of https://community.atlassian.com/t5/JIRA-discussions/I-created-new-status-quot-Blocked-V-quot-for-a-bug-not-able-to/m-p/590464#M280
-
Either a user can see an issue or they can not. If they can not see an issue, then they can not get any data on to a dashboard about it, it's not something they can see. So, no, natively, JIRA won't let you leak information from issues people can't see. You either need another tool that can check JIRA for the dashboard…
-
No, the boards are configured separately as teams using them may have different needs.
-
I'm afraid "make them more simple" will generally end up with "make them less powerful" The defaults, with "can log in" groups going into every project automatically should be changed, but if anything, the permissions schemes need more complexity as it would be better to separate some of the permissions more!
-
The data you are trying to display is global, but you want to see it within the context of an issue, which is why you've ended up looking at fields. I'd stay away from issue fields because although you could write a field that would hold the number, it's not an issue field. I would write a new panel for the issue view…
-
No, there's no global settings - boards are intended to be configured to suit the individual groups of users who use them.
-
You'll need to find or write an add-on that implements a "web fragment" that inserts itself at that point in the UI
-
I suspect this is because JIRA is not clear about what it is ordering by when you say "order by fixversion". It's not using the name of the version, it's using the database ID. Try renaming your versions and you should find the order does not change, as it's the underlying id that matters. Unfortunately, there's no real…
-
Subtasks are useless noise on backlogs, as it makes no sense to rank them outside their parent issues. So the backlog ignores them. Simple case, imagine you have * ABC-123* ABC-345 * ABC-789 * ABC-456 * ABC-234* ABC-567 * ABC-678 If ABC-123 is ranked higher than ABC-234, then it's more important. ABC-567 therefore cannot…
-
You do not have a valid licence for the add-on that is providing the "set value of field" function that you are using (presumably JMWE) There is a built-on (and hence free) function to "set field" - you should give that a try, although I am not sure it supports the estimate field (as changing the remaining estimate breaks…
-
The audit log is off by default, you may need to check that it is turned on.
-
You say "your JIRA", which suggests you mean it's an Atlassian Cloud system. To "uninstall Agile", you would go to your account and remove the "JIRA Software" option, remembering to retain "JIRA Core". For Server versions of 7+, Ann's answer is correct, except that JIRA Software is now handled in "Manage Applications"