Comments
-
No, it's not. That's the point, the project key in it gives the user enough information to filter for "I know what that is". Raw numbers do not. It doesn't matter how often you deny it, it's really simple - informational IDs are better for humans than abstract random ones.
-
You're misunderstanding. I work with people who have picked up a handful of issues as being important. The project identifier often means they can identify them from memory. They can NOT tell the difference between 456234 and 455324, but if you say ops-456 and dev-455 very easily because they're relevant and have useful…
-
Yes, everywhere I've worked, people are able to use Ops-123456 without referring to a system to look it up. It already tells me "it's the Ops project", which instantly puts the user in a position where many of them do not need to look it up. A random number does not do this. They do NOT memorise arbitrary and uninformative…
-
I'm not sure what is "different things" here. You've got a useless unique ID that people have to actively look up before they can do anything useful with it, against a unique ID that has some informational content that humans can use. You're wasting a lot of time with the low-information ID, and it really is of minimal…
-
You're ignoring the context of the question I asked. Given 12345, can you tell me what project this is in? No. So a non-informational id fails. In human terms, generally, yes, most people DO know what project shortcodes mean. Let me rephrase this from a human point again, as you seem to be missing what I'm getting at…
-
But the point here is that you simply can't answer the question, so a non-informational issue id instantly fails. Now imagine a system with several million issues and thousands of projects. From a human point of view, it ABSOLUTELY matters that you can get grouping information from the issue id. 1013312312 vs 22341987 is…
-
No. Because an issue without the project key in it won't look like it's in the project. Here's a really simple example. I've got three projects in my dev system, and around 30 issues. Projects are Weebl, Bob and Chris. 10021 is an issue id. Which project is it in? If you think you need an id without the project then you're…
-
Yes, it does. An issue is shown as belonging to a project by having a key of format <project key><sequence>. You change project, you must change key to match. That is totally separate from the issue ID, which is in the Jira database and does not change.
-
As Jobin already said, no. The Issue key is always <project>-<sequence>, so if you move an issue into another project, there is no choice but to change the key. The old key remains in history and is searchable.
-
Ok, I'm afraid there's not a lot to do there, the macros have been used as content, rather than in the structural stuff, and the nature of content is that it can't be mass-updated easily There's three basic approaches I would think of. A bit of analysis on each macro (including a search, as it does let you at least say…
-
What elements of a page are you trying to change globally?
-
A blueprint helps you build a page or space initially, but it's not structural. It's like a recipe - you can use it over and over to make cakes. But if you add more chocolate to the blueprint, it has no way of going back to add chocolate to all the cakes you made before.
-
Try installing the Kepler custom fields addon in the target JIRA and retrying the import. I've run into this error a number of times, and it's not just the Kepler ones that do it - it's often worth making sure you have the same addons installed in the target (compatible versions of course) as you do in the source JIRA when…
-
Yup. Another way to put this is simply "make sure the filter for each board includes the issues you want to see on those boards"
-
For JIRA, your JIRA username and password. For Google Calendars, use the google account details that the calendar is trying to read.
-
I'd change the workflow and process to block that.
-
The migration will be asking you to do this, as it has no idea what to move the issues on the deleted steps to. You can ignore it when it's saying "0 issues affected", but the rest need to be mapped.
-
>Had to cancel the migration as too worried Good move, if you're unsure! The point of the migration is that if you remove steps that Issues are currently on, it MUST swap them for something else in the new workflow. Otherwise you end up with hanging issues that you can't do anything with (i.e. a broken Jira project) The…
-
I don't quite understand that - when I create a new scheme, the drop-downs list all the current available workflows, irrespective of their active/inactive state. However, drafts are NOT included on that list - could that be why you're not seeing it? You're working on a draft instead of a copy?
-
Deleting steps is something you can't do in draft. It's too hard to do the data integrity. Copy the workflow, delete the steps from the copy, create a new workflow scheme, put the new workflow in it, and change the scheme at the project level. It will take you through the migration. As a short term fix though, you could,…
-
By "won't work", Jobin means that there are some edits you can't do to a draft, not that you can't "publish" them.
-
You really should avoid using SQL for this sort of thing. But if you insist on doing it the wrong way, look in the issuelink table - it's got source, destination and link type (although you'll need to look the issue ids up in jiraissue and the link types in issuelinktype)
-
Argh. They are in the download version, so you can extract them from there, and they're useless to you because they are compiled classes. If you want to use them as example code, then you need to download the source, as Renjith suggests. When you compile that source, you end up with them amongst other things.
-
That's simply not going to help you. Whatever you're seeing in the wsdl is what is exposed by the SOAP interface. Trying to add classes from internal functions into your application is pointless because the functions are intended to be used inside Confluence. You still need to talk to the Confluence installation remotely.…
-
Those are bundled in with the off-the-shelf distributions. They aren't generally available separately because you should need them separately. You can just download the relevant versions of Confluence and find them inside there of course, but I'm curious to know * Why you think you need them * What they've got to do with…
-
Sorry, "populate user in dashboard" does not make any sense at all. A dashboard is a collection of gadgets, not users. What do you think "adding a user to the dashboard" will actually do? What gadget changes?
-
What's a "managed dashboard" and what do you mean by "add user"?
-
No, you can only bulk-change issue types at the same level. Sub-task to sub-task and parent to parent.
-
Good point - if the field is on the edit screen and the source and target types are configured the same, a bulk-edit -> edit will work. If not, then use bulk edit -> move and it will ask you all the necessary questions (starting with target project which you leave the same, and target issue type)
-
Use bulk edit. https://confluence.atlassian.com/display/JIRA/Modifying+Multiple+(Bulk)+Issues