Comments
-
Thanks Udo - I can never remember the name of that table, just that it's got sequence in the name. You need to understand the counters/sequences in that table in great detail, because you will make a right mess if you get even one of them wrong. As I said before, PLEASE, use the importers, not SQL
-
Yes, sorry, there's quite a lot there! 1. You need to replicate what Jira would do if you were using the importer. For each issue you raise, there is a unique ID in the database. Jira has a table saying "next numer is xxxxxx" and for each issue, it grabs a number and increments the counter so the next issue has a new…
-
No. You will break your Jira. You need to work out the next free value from existing data. For every issue.
-
I would avoid an ETL, because you really do need to know the database in a LOT of detail to be able to import data. To run you through a single issue import in a generic way, you will need to: * Stop Jira and get a full backup. (NEVER never never write to an active Jira database, and if you insist on writing to a shut-down…
-
1. Draft workflows cannot do everything. To delete a step from a workflow, you need to copy it to a new version, remove the step and then migrate the project over to the new workflow. This is because drafted workflows don't have the code behind them to cope with the potential data migration required when you delete a step.…
-
Your expert is correct - never touch a JIRA database unless you have to, and certainly not to hack something like that in. JIRA Software expects Epics to be a single Epic issue type. Botching in another one is not going to work. Even if it appears to on the surface, it breaks in interesting ways later, and a lot of add-ons…
-
That's a matter of education - we make it clear to users that "duplicate" really does mean "logged somewhere else". We also exclude them from release notes.
-
Sorry, hit return too quickly.As an admin, you will be able to check the permissions on the space and make sure you have edit for the page, and you'll be able to see any page restrictions that may stop you from editing as well.
-
So? That means you have admin rights. Not edit.
-
The move options gets disabled when you do not have edit rights on the page.
-
Look for server versions of the three Atlassian products at https://www.atlassian.com/purchase/ And https://marketplace.atlassian.com/ for the addons (IDE connector)
-
Click through from the pricing - see https://www.atlassian.com/software/jira/pricing
-
I forgot - some gadgets have a "ignore resolved issues" flag. So you could put two gadgets next to each other, with the same filter, but set the flag differently.JIRA doesn't do "generated" fields, other than the built-in ones (mostly to do with sums of time tracking). But if you have one of the scripting addons that does…
-
There isn't really one for resolved/unresolved directly, but you can get close. Define a filter for "issues in priority X I want to look at". Add a "filter statistics" gadget using that filter and select "resolution" for the field to report on. It will give you all the resolutions separately, but including "unresolved" and…
-
Yes, changing the workflow affects the existing issues. Let's say you have a project with Bugs, Story and Improvements. Your workflow scheme currently says "use 'general' workflow by default", so all of them use the workflow called 'general'. Your new setup needs to have a workflow scheme that says: * Bug: workflow called…
-
No. A group really is a name and a list of users. There's no other structures you could hang any data on. I've seen a form of group management in JIRA though - you have a project called "groups", with one issue per group, and whatever metadata you need attached in there. It has to be manually maintained, and you need extra…
-
You are correct, templates are not versioned.
-
No, you're correct, permissions (such as "edit issue") are done at a project level.
-
No. Security and permissions are done at Project level, not issue type. There are some work-arounds: The obvious one is to set up a security scheme and then automatically set the security level with a snippet of code in a post-function. That would mean users could create issues of a type which are then automatically hidden…
-
No, there really should be something in the log to tell you what it's doing (I'm assuming you mean that there's only 1 user and that's the admin user?) Might need to run the JVM with verbose logging on to find out what it's actually doing.
-
What does your confluence log file say? How many users are there in the Jira database (sounds like just 1, is that right?)
-
Yes, well worth moving to Confluence.
-
What post-function are you using, and what "doesn't work"? Are you getting errors in the logs? (I assume no sb-tasks are created, but there may be other symptoms of "doesn't work")
-
Ah, this is one of the somewhat confusing things with the divergence of the three JIRA applications. Issue collectors are an old function that JIRA projects had to help with testing and, well, collecting issues from applications. Bypassing the long dull history, the short story is that they're JIRA Core functions, and to…
-
Depends on what you mean by "macro" - where do you want to be doing the "click on something and get a new jira issue"? If, for example, it's another Jira issue, then you probably don't mean macro, and you'll need to explain more. If it's Confluence, then the latest version has issue creation built into it. If it's another…
-
I would, based on what you've asked. The two systems are similar and need to be kept in line, so it sounds right to me, otherwise you're into maintaining 2 nearly identical projects.
-
I'd be tempted to do it all in one project, and then have a custom field that indicates whether it's for the side project or not. Might that work? Could try components or labels to do the same.
-
We don't know what timesheet add-on you are using, but the best bet is to ask your JIRA administrators first, as they may have to do it.
-
I think you need to read the log file to get more detail, I'm afraid this screen is not extracting and displaying enough information to tell you what has gone wrong.
-
What user directory is the old system using? And what is the new one using?