Comments
-
Yes, you'll need to work out every possible combination - each one will need to be searched for and edited separately.
-
You're going to need to break your search into pieces and use bulk edit on each piece. e.g. for issues with "core", do one edit, then for issues with "core" and "ce" a second batch, then for "core","js" a third batch. Or, just rename "core" to "html", if I've understood that you just want a simple "replace" function.
-
I'm aware of that, but your "question" doesn't say you've got any problem or what you're trying to do, so there was no point mentioning it until it was clear what you wanted to do. Which still isn't there. Please explain what you are actually asking for here.
-
There is no question here, so there's not a lot we can tell you. Jira has a bulk-edit facility - that is probably what you need to use.
-
are you trying to render this richly, or are you trying to show the plain markup as it is?
-
It's not clear what you are trying to do here, or what you mean by "replicating". The text you've given is wiki markup - are you trying to render this richly, or are you trying to show the plain markup as it is?
-
Ok, sounds like you haven't uploaded the backup from the source system up to the target one.
-
Yes, that's the procedure - backup, then import. Could you tell us what your actual question is here?
-
To the last sentence, I'd add "collaberation abilities are being *noisily* added to Confluence"
-
You've almost certainly set it mandatory in the field configuration, although you might have done it with a workflow validator. Do you have the field on screen though? You should only ever put resolution on "issue view" (not that you actually need to, as JIRA will display it whether it's on the screen or not) and…
-
Yes, but you will need to have a status in your non-simplified workflow to put into the column
-
You can have whatever columns you feel you need in a scrum board. Just add one called "blocked" and put at least one blocked type status in it.
-
I'd add that "clustering" is no longer supported - you'll need to look at Confluence Data Centre (after database tuning and hardware improvements). Also, I've looked after healthy standalone Confluences much bigger than 80k, so you can get a lot out of decent hardware and database tuning!
-
There's no screenshot. However, you should be able to simply edit the sprint using inline editing on each issue
-
None yet - Jira doesn't track most admin changes (you can plough through access logs in some cases, but they won't necessarily give you any details.) There's a plugin which tracks admin changes, and I understand Atlassian are looking at some logging of admin changes too. But there's nothing in 6.1 or below natively.
-
Slightly lazy design or coding I think - the screen doesn't bother to read the current issue type scheme, because it's easier not to.
-
It is doing what it says - it needs to know what to migrate the current status to. There should be a count of the issues affected next to each one though - if that is zero, you can accept the default and ignore it, as it won't have any effect.
-
That is pretty much it - Streamwork would be able to draw in and display information from Atlassian systems, but nothing more. Unless you wrote stuff to enable updates in SAP from gadgets.
-
If the database is unharmed, then in theory, a 5.1 install will simply upgrade it. But I'm doing that at the moment for a large site (specifically 4.0.2 straight to 5.1.8), and we've run into problems with users, greenhopper mangling fields and a whole host of "custom code"/"plugin works differently" issues (sadly,…
-
Eek! Totally agree with that - get a backup before touching anything, and then download a copy of Jira 4.0.1 and get that working with the data first. Jumping versions at this point is a potential disaster, especially if the database has been damaged in any way, as it'll make data repair a LOT harder. In theory, you should…
-
See https://confluence.atlassian.com/servicedeskcloud/creating-service-desk-request-types-732528762.html Oops, sorry, a bit too quick. See the bit that says "On the Workflow Statuses tab, you will see the default JIRA workflow status names displayed on the lefthand side. You can change how these statuses appear to…
-
Two options * Service Desk Requests can show the customer a simplified status that differes to the actual workflow * You can with a bit of code to calculate and populate it.
-
Ah. Sorry. I misunderstood. There are no fields at a project level, so you cannot do this natively. From memory, there's a plugin called "profields" which allows you to add project level fields and I think that will do most of this for you. You could try to do it with project categories as well, although they are not…
-
No. The list of available priorities is shared - if you've got 7 priorities, then all projects will let the user choose any of the seven.
-
Hide it. Create a permission scheme that does not have anyone set for "browse". Then no-one will see it, it won't turn up in searches and it won't be offered in drop-downs. If you do still need to see it, then you could use a permission scheme that only allows "browse". At least that way, it will not be offered in the…
-
To the top right, in the workflow scheme definition screen, you should have options, including "associate new issue type"
-
You can, yes. Update the workflow scheme, and you'll find JIRA asks you about how to do the migrations.
-
I suspect you don't have a use for 99% of the things in bugzilla as well.
-
Atlassian have ruled out clustering for the foreseeable future. You are going to struggle severely with 10 million issues in a single Jira instance, no matter what your hardware. As a guideline, Atlassian were recommending splitting Jira when you approach 200,000 under Jira 3. This has increased a lot since version 3, but…
-
I'm sorry, I don't understand the question really. Same field as what? Same workflow as what? By different transition (postfunction)? (postfunctions are added to transitions, they're different things?) Is this the same question as https://answers.atlassian.com/questions/240330/update-the-field-while-creating-the-issue…