Comments
-
The third line from the bottom of that log tells you why you can't reach it. It's not running on the port you're trying and it's giving you a different location. Try hitting that instead. Atlas-run does this sometimes when you're already running something on the ports it wants to use.
-
I'm sorry, I don't understand. Issue assignments have nothing to do with configuring issue types ti use workflows. The second part I think means you're worried about affecting other projects. Yes, you will, if the scheme is used by other projects. Although it only matters if the projects are using that issue type (that's…
-
It's not "adding it to a workflow". You go to the workflow scheme and tell that to use your chosen workflow for that issue type. JIRA will migrate any existing issues when you commit the change.
-
As long as the JIRA installations are the same version, you will be fine. See https://confluence.atlassian.com/adminjiraserver071/restoring-a-project-from-backup-802592982.html
-
No, it's very very sensible. If I change a template, in the overwhelming majority of cases, I don't want that change to go destroy what I had before.
-
I'm afraid the really short answer is "no". That's not what templates or blueprints do. They create pages when you use them as starting points for your work. Changing a template or blueprint later has no effect on existing pages because they're there to help you create new stuff, not change the shape of old stuff. (In…
-
It's as the docs say - you create a new workflow scheme, and either change the "default workflow" or add an issue type to it. It doesn't matter that it says "inactive", all that means is that you have not yet associated it with anything.
-
You see it in panels here, not sentences or words. And try looking at the world's biggest wikis - they're all black on white or pretty close to it for over 90% of their content - panels being used for callouts and highlights.
-
Yes, sorry, I said the {bgcolor} macro before, but didn't point at it, and I shold have. It's in the Adaptavist stuff as Peter says. (I should say I work for Adaptavist for the sake of openness, but it was written a long time before I started there...)
-
That's the thing, changing text colour is not that common. People do use it, and they do ask, but it's really not used as much as a lot of people think it is. Background colouring is even more unused, and people simply don't ask for it enough to make it worth implementing. I've also found good reasons not to use coloured…
-
Because it's not a common thing to want to do in a set of documentation. Remember this is a wiki, not authoring or design software - the content is vastly more important than the presentation You can, of course, do it, just not in the basic editing function. I've used the {bgcolor} macro to do it, as well as {panel} for…
-
I think it's important to mention that many of the "permissions" are actually just flags that get used by various bits of code. For example, the permission "edit" is used by the code that provides the "edit" link and the "inline edit". In the case of "close" though, it's not really directly coded. It used to be that the…
-
What condltions do you have on your workflow? Specifically the conditions on the "close issue" transition(s)? It sounds like you may have checked the users access and membership of various groups and roles, but not put any condions on the worfklow, so the actions are wide open. If I'm right there, you probably want to add…
-
Issue level security lets you do this within projects. https://confluence.atlassian.com/display/JIRA/Configuring+Issue-level+Security
-
You shouldn't need Gears any more - see https://jira.atlassian.com/browse/CONF-26080 for why, but I think you'll need to do a bit more debugging on exactly what is enabled/disabled in your IE9 installs!
-
* No. They will get it wrong and break each other's work. Atlassian is working on delegation, but we're not there yet, and I've spent most of the first year of every Atlassian job I've had sorting out the mess made by letting project leads/managers have admin * Yes. And use it for change control too (I want a new workflow,…
-
No. I'd leave them alone. However, I would, if possible, remove the "issues" directory underneath it - a couple of times, I've seen "full re-index" not quite clear it out. (If in doubt, move it, rather than delete it)
-
No. You should not need to re-index after delete. Or bulk-edit. Or anything else you do in the UI. However... there is a bugette in Jira somewhere that causes this error - I've never got to the bottom of it, but neither have I ever been able to tie any problem to it. So, I think it's (mostly) harmless in that it won't…
-
It could be on your own Jira install - it's as simple as changing one or two text files, adding *maxlength="100"* to them and restarting Jira. But I don't think OnDemand will let you do that.
-
It's a 254 character string in the database, and the html lets you do that. There's very little reason to reduce that, which is why there's no option in the UI (Over many years, I've seen a couple of dubiously-reasoned requests to increase it, but I think this is the first to reduce it) If you had your own install, you…
-
It depends on how you remove the field. Derrick already covered two cases: * Removing from the screen - no effect, other than you can't see it (Assuming it's removed from the view screen) or add/amend values (if removed from Create, Edit or transition screens) * Deleting the field from Jira - gone, dead, need to go to a…
-
What errors are you getting, and what does the log file say?
-
I think the search stemming means that it needs API to be a separate "word" in the title of the document. The indexing is seeing the API as part of a bigger "word" because it is embedded in a string with other characters. To the indexing functions, I think your page title looks something like xxxxxxAPIxxxxxxxx, so it's…
-
The user's email address is part of their profile and can be set by the user, or by admins editing the account. Please read the links Rambanam has been quoting, they really are the right place to read about basic maintenance of Jira.
-
I think the rating is because posting a non-question without discussion or explanation can be taken as quite annoying. You're not giving the community an opportunity to offer you any help or interaction, just appearing to be taking a swipe. Most of us ignore it, some give you tongue-in-cheek responses asking for some form…
-
There's plenty of answers around. But to find them, you need to actually ask the question!
-
Then you need to add it for them when creating new projects. The defaults for JIRA project creation have changed, you need to adapt your processes to deal with the changes.
-
This is not about backwards compatibility, it's about the configuration of your system. You have removed "task" as an issue type from the project(s) that your customers are using. Add it back, and it will work again.
-
No, versions exist at project level, not component.There is a feature request open with Atlassian for versions of components, but I Don't have the link to hand.
-
It's not limited to any number you'd need to worry about - lots of thousands - far more than you'd ever have any realistic use for. But I'd recommend splitting the project up if you have a lot, as it'll become unwieldy and difficult for the users.