Comments
-
If you are using OnDemand, then you can not. Standalone, the default user you create during installation has full rights. If you didn't set it up, then you'll need to get the administrator to add you to the system admin group
-
Ah, ok, a simple migration is easier. You have two things to consider - the database and the "home" directory. The home directory is simple - make sure the files on the new machine are a direct copy of the ones on the old machine. The database is a bit more complex, but the principle is "connect the new installation to the…
-
Well, you can still upgrade, but only to a version that was released while your licence was valid.For example, if your licence ended on 1st December 2014, then you could upgrade as high as 6.3.11, but not 6.3.12 (that came out after the expiry date)
-
Yes, javascript is a very good way to do it, you're spot on there. It is a sticky problem because of the basic question - how does the client know that data on the server has changed? Exactly as you say, the only way to do it is "unnecessarily" poll the server regularly. That feels wrong to me, but I can't think of a…
-
Er, how do you expect a client browser to know when information has been updated on a server? Think about this carefully - Jira has a load of information that it shows to a user who asks "show me this page". If you want an "automatic" update, then somehow, you need the *Server* to tell all the *clients* that something is…
-
Yes, but I doubt you'll need it - the backup is more to a) keep a copy of the workflow and b) give you something to refer to if you think you might have damaged it. Even if you completely mangle your workflow, it's generally easier and nicer to fix it and carry on that revert to a backup!
-
No one. Click on admin > import/export, use the backup option then download the file it creates
-
Check the permission scheme - there's an explicit permission to allow "delete worklog". You need to make sure you match that one.
-
Yes. It's probably easiest to grant "anonymous" read-only access to the space(s) you want them to see.
-
There's no real "delete" - Atlassian need to keep them for regulatory reasons. You could ping support and get them to deactivate the one you don't want, but the simple way to "quit" the account is to stop using it.
-
Yes, I'd go for Bob's CLI if you have it. I'd be tempted to try it with script-runner (mostly because I can now throw things at Jamie's team when I get stuck) and for a shell script, I think I'd try an iterated REST call to JIRA
-
Not really - you needed to attach the attachments at import time, as JIRA needs to populate the attachmnet table. There's no scan ability, if you want to "repair" it, you can either upload them via a script, or try to hack them into the attachment table (Which is, of course, risky)
-
I don't think you're wrong about linking the bug to the stories, when it's appropriate - you're saying "this bug has something to do with this story", it's just that you don't seem to know whether the bug should be part of the story or not. You're strongly leaning towards it not being part of the story, but then expecting…
-
p.s. that comment was a bit longer while I was typing, but @mother-goose has said a lot of what I was trying to type, and it's a better write up than I had.
-
But you said you don't want the linked issues to be part of the story. I'm sorry, we're going in circles here. I can't work out if you want the linked issues to be part of the story or not. If you do, then they should be sub-tasks. If you don't, then you're fine as you are, but you won't see them in the swimlanes, because…
-
Yes, that's fine. But you then say you want see linked issues as part of the story. But you don't because they're not part of the story. Which one is it?
-
But that contradicts what you're saying about them counting towards progress on the issue. I think this needs to go back to making a solid decision about whether they're part of the story. If they are, then make them sub-tasks. If they're not, then links are a good way of indicating a relationship, but they're not part of…
-
So, why aren't the bugs logged as sub-tasks? They belong to the stories from what you've just said.
-
So, you're defining things that are part of the story as not being part of the story. This isn't a limitation in the software, it's working logically. If your bugs are genuinely part of the story, then treat them as such. If they're not, then don't expect them to appear with the story.
-
Ok, this seems wrong to me: >It's not right for us to raise them as tasks against stories ... as they are not tasks to action, they are defects. If they are separate defects, then you don't need them in the swimlane. They could be related to the issue, but they're not part of it. If they need to be closed off before you…
-
You can't. JQL returns a list of issues based on some criteria, but the JQL is not the issue. The board is coded to display stories with their sub-tasks when you select "swimlane by story". That's it. Linked issues don't matter to the swimlane. You can get them on the board if the filter is clever, but they won't land in a…
-
Oh, I see. The older upgrade method was renamed as "upgrading manually". Yes, you need to do it this way to get on to Confluence 3.5
-
Not sure what you mean by "manually", but yes, it's very strongly recommended that you go 3.5 before you attempt the jump to a later release. A lot changes between 3.4 and 3.5, and it's a nightmare to go from 3.4 to 4.0, let alone higher!
-
Ok, so testing other pages is a good thing, but I think you need to explain "does not load" in a bit more detail - is it a white blank page? Just the menu? Is it when you're logged in only (i.e. anonymous users who haven't logged in yet are ok). Gadgets appear but no content for them? Also, how much have you got on this…
-
If it can be loaded locally on the server, then the problem is being caused by your network - you'll need to check the route between the client and the JIRA server.
-
Use a browser that still supports NPAPI, and wait for Atlassian to code a screenshot trick that doesn't need it (remember, it's only the screenshots that break)
-
If I remember correctly, NPAPI in Chrome is a support library for chrome addons. JIRA is server based and doesn't need any browser addons. If you want some evidence, Chrome on Linux had it removed in version 30-something, well ahead of everyone else. I'm typing this in version 41 on a Korora build, and there's a couple of…
-
I can't make out much of a pattern to be honest - most of the time, you need to restart. But not always. I just work on the assumption that as soon as I change something, what might happen is a grey area until I restart.
-
You don't always need to restart Jira to pick up template changes - it reads the email templates on demand, and if it hasn't used one for a while, it may have dropped out of the cache, forcing it to re-read the .vm (which you've changed) I suspect the fact the messages started before you restarted is a bit of a…