Comments
-
Ouch, that's not a fun job. You will probably find it a LOT easier to consolidate the user names, or use Crowd's user Alias function to do this. But if you must delve into the database * jiraissue - assignee and reporter * nodeassociation - voters and watchers * customfieldvalue - user picker custom fields * worklogs - for…
-
The only field you can do this with (without coding) is resolution. You could try to do this with a bit of javascript or maybe the behaviours plugin (I've not tried it with that plugin, so I'm not sure)
-
It's working for me, which diagram is broken for you?
-
No, you need a valid licence to upgrade. There's no "discount", as you've not been paying the maintenance, you'll need a new full price licence. You can retain all your data, either by importing or upgrading in situ. The best option is to get the new licence and install it now, then follow the upgrade documentation -…
-
I'm afraid Anthony is essentially correct here. Confluence-users is a group that says "can log in". If it's used in permissions to allow any more access, then all users in the group will get it. So you *must* unpick that if you want to restrict someone's access. Daniel's solution is one approach, but has a significant…
-
Well, you could get the users to start ranking them - the priority is shown on the planning board, and you can easily select batches of issues, right-click and push the selection to the top or bottom. You'd need to weigh up the value of asking the users to do that over the effort required to script it (the stuff I saw was…
-
Very true - the problem with any automated/bulk re-ranking is that it could easily mess up everything your users have already set up.
-
No. The problem here is that a rank is a reference to a unique place in a list - each rank effectively describes a position between two other items - "I'm above that one and below the other". Bulk edit changes a field (or set of fields) to a set value. Because the ranks are effectively unique, you can never logically…
-
Atlassian tend to code for the majority of their users, it's not a case of being "right". I'd say not putting "invalid" things into the release is the best option - you're right about the author of the changelog thinking about it, and the results of that thought should be accuracy - "we didn't do bug X, so we shouldn't…
-
Ah, the release notes. They cover everything, unfiltered, and that's accurate and what most users want. If you want to drop them, then your best bet is to reflect the reality of what you're doing. Search for all the invalid issues and edit them, removing the fix-version (or changing it to something else)
-
What's the "changelog" page? (I ask because there's several things you might be looking at here) Although, I'm not sure a filter is of that much use to users in general - a lot of use like to see issues that have been written off as invalid in software updates.
-
Permissions are always worth checking first! :-) Could you check the application logs to see if there is any more information on the error in them? It might have an error code or more detail on what the OS is telling it about the directories.
-
You can get this error if the user running confluence can see, but not write to, the directory/drive that it is pointed to. Check the permissions allow it full control of the target directory.
-
Duplicate of https://answers.atlassian.com/questions/44897735
-
Confluence is a wiki - you add and update the body of pages as a whole. It is not intended to be a form-based application, it's for free format pages, and the closest you can get off-the-shelf is to use templates (which still aren't forms, they're just pre-population of standard data) There are a number of plugins which…
-
Ok, so you've got DDTS-ID, but you haven't explained what you mean by "as external field", or how you are storing the relationship between that and the Jira issue. Could you explain these two? I'm pretty stuck until we know the structure of the data.
-
You need to define the logical relationship before we can help you answer that question. How do your systems know that Jira-X is linked to External-Y? As a quick example, maybe you have a custom field called "external id". If that's true, then you can search Jira for "external id = External-Y" and you'll get one (or many)…
-
You need to define the logical relationship before we can help you answer that question. How do your systems know that Jira-X is linked to External-Y? As a quick example, maybe you have a custom field called "external id". If that's true, then you can search Jira for "external id = External-Y" and you'll get one (or many)…
-
Not directly in the way people think it could be done, but it is possible. You can not do it with permission schemes - these affect the entire project and do not apply to issue types. You can do it in the workflow though. Set up the permission scheme to allow everyone to do what they need to do across the entire project,…
-
That's fine, my point is that what plugins do what are totally irrelevant. Macro X does Y is perfectly sensible, and it's the way Atlassian have documented them at https://confluence.atlassian.com/display/DOC/Macros - that will always cover the macros a plain installation of Confluence will provide.It's generally good…
-
I was curious as to why you think it's useful to try to compare Cloud and Server versions in terms of plugins, as most answers to that question probably have a better approach.This one certainly does - 99.99% of users simply don't need to take a "this system plugin does that" approach to Confluence. Use Confluence…
-
It doesn't matter - they're the ones that make Confluence work when you install it off-the-shelf.I'm not sure why you think you need to know this? Run a trial of Confluence, if it doesn't have something you need, then look for an addon to provide it.
-
Basically, the same - you get all the system addons, and none of the others.
-
Why are you trying to do this? I don't think it's going to be a case of Jira supporting it, it's more that just downloading things and stuffing them into a Jira installation without configuration (or even any reason to do it) is going to be useful.
-
You have to use html on server, as it says in the description.
-
Ah, no, that makes sense, you do need browse to be able to see the issue to which you want to attach it, so you must grant browse project to them. To hide other issues, you usually use the issue security schemes (The reason I said "usually" is that if you want "reporter can only see their own reported issues", you can…
-
Ah, crossed comments, sorry! Ok, the key of PROD rules out what I'd remembered (a numeric project key causes this problem), so a few more debugging questions * When does the message appear? After selecting the file add, or the click of the button to commit the change? * Can you have a look at the log file around the time…
-
Hmm, I've seen that before, can you tell us what the project key is? Also, can anyone attach it, or is it blocked to everyone?
-
Could you give us the text in red? The screenshots are too low-res to make it out.
-
Not as the key on the Jira issue. The CSV import is sequential, so if your external system has (say) ABC-123, ABC-125 and ABC-126, you could import 4 lines of CSV - plug the hole at ABC-124 with a dummy issue and delete it later. But bear in mind your project key will need to conform to Jira standards. Most people doing…