Comments
-
Ok, but that's just a case of clicking it when you know you've finished your changes, exactly as Ravi said. The REST call does that You do not need or want to do it regularly.
-
It's always worth questioning why you want to do this. There are some cases where it makes sense, but if you're doing it because your index is regularly going wrong, then this is absolutely the wrong thing to do. There's a phrase "plastering over the cracks" - when your house is structurally unsound, cracks appear in the…
-
Ok, you'll need to find or write code to do this. It sounds like it needs a "service" so it can run at specific times, and you'll need to think through how to identify what you want to merge and what data is copied and/or deleted.
-
I think you'll need to expand on the question a little. What would a "copy" actually do? If you're expecting the source issues to go away, is this actually a merge? If it is not, I'm not sure what you expect from the copy. If it is a merge, then I can imagine logical paths for the history and comments, but what do you do…
-
Yes, as long as you are publishing that file somehow. If you can open it with a browser (NOT a local file share), then you can include it using the html macros in Confluence.
-
Best guess: wrong version of Java.
-
What does the log file say?
-
You do not have the right to add full Confluence administrators, that's restricted to Atlassian.
-
That's a very complex task you've set yourself. The SQL for getting it out as a single query is far too complex and includes the need to parse xml while you're at it if you want a proper accurate answer to "who can do what in my project".I'd go back to your users and ask why they need this and tell them that it's a small…
-
There is not a simple way to do this. As a member of a group, I could have a project permission granted to me because: * The permission scheme uses the group * The permission scheme uses a role and that group is placed in the role * The permission scheme uses a custom field and the group might be named in that field which…
-
BetsyW >BTW, is there (or shouldn't there be) a limit as to how many questions one person can ask? No, there shouldn't be a limit. Questions to which the answer is "what does your log say", "here's the documentation" or "LMGTFY" should be limited though...
-
Eh? It's not retired, it's still there in 5.8, 5.10 and Cloud. My guess is that one of your admins has disabled it, or removed your browse-users ability.
-
The only other issue is if people have used the old url in links or external systems, but that's purely a data issue, it won't break anything in JIRA.
-
Um, no. We don't have access to your servers. You either need to read the log files in more detail (you'll find this stack trace in them, but more above or below that will probably tell you more about what's going wrong). Or contact Atlassian OnDemand support if you're using OnDemand
-
Filters do not belong to projects, they belong to users, so no, there is no way to "disable filter management for a project". The relationship isn't there, there is nothing to do. As for "include information that should not be shown", that's also going to run into the "filters belong to users". The important thing here is…
-
Mmm, that's nothing like what you originally asked. First, can you confirm that the original code worked before you starting amending it? The Word export stuff you had before you started amending the template will have displayed the data you are looking for. Secondly, you should look to reuse the code that works there as…
-
You don't need to do anything if you're using the standard custom fields, or, in fact, most other custom fields. They display in Word automatically - if you can see them in the standard issue view, then you should get them in the export as well. Could you tell us what fields are not appearing - specifically, what type are…
-
You don't need to do anything if you're using the standard custom fields, or, in fact, most other custom fields. They display in Word automatically - if you can see them in the standard issue view, then you should get them in the export as well. Could you tell us what fields are not appearing - specifically, what type are…
-
I've not been able to find one, but the marketplace might have something if you can form a better query than "SCCM". If there is nothing,then consider writing something yourself - you'll need to think through what you want from "integration" and how to do it (add on in Confluence, user macro, external calls over the REST…
-
Have a look at https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.ext.subversion/server/overview - that does exactly what you want to start with - scans commits. I'm not saying it's the right answer for you, but the source code is available, so you could use that to guide you on reading Subversion
-
I'm sorry, I'm not sure I understand that really. I think it's just the language - I'm thinking in Jira-speak, rather than English. 1) You don't close an issue with a post-function. You close issues with a transtion. The transtition can have post-functions, and if you are ok to always use the same resolution (which is NOT…
-
I suspect your workflow and/or screens is not using "resolution" correctly. Could you check where you are setting and clearing the resolution? Post-functions? Do you have it on any screens? Even if you've chosen not to use resolution, you need to deal with it for Jira to function correctly.
-
It's buried in the system add-on that provides the field. Don't mess with it - you make your system unsupportable, and there are other places that assume the status lozenges are a certain width, so if you change it, you're going to find you need to re-engineer a load of other things too (also scattered across bundles and…
-
https://confluence.atlassian.com/adminjiraserver072/upgrading-jira-applications-828787633.html You should find you can go straight to 7.2.2
-
Because there's no use for it. As described above. Well, there are some uses mentioned, but in the real world, it's easier, faster and more useful to achieve the same end goal in other ways.
-
Mmm, testing stuff that isn't like production doesn't sound that useful. And if you're testing stuff to go into production, well, it's going to change anyway.
-
More suitable than what?
-
No, you have to be an admin to change workflows (and this changing of IDs is pointless too)
-
What do you mean by "key name"? The label of the transition (the "name" the users see) is editable in the UI.
-
Ah, good. I'd be trying to use something other than the ID, as it really is effectively a random number, but this works, and I'm an engineer (so "if it ain't broke, don't fix it" is instinctive)