Comments
-
The problem when you split things is that there's no logical tie between them - you don't know the difference between a split and a few issues that have been created together. What I would do is promote the story to an Epic and then break it down into smaller stories and tasks. Another option would be to link the issues…
-
That's provided by an add-on. There's actually a few that do it, but I suspect you've hit the "issue hierarchy" add-on. Ask your admins what add-ons you've got and if any use that word in their name.
-
The trial software is not really a trial. It's the software in full. The trial is simply "everything" with a licence that says "stop working after a trial period". To move from a trial to a "full" version, you can just buy a licence and apply it. Your trial/demo data will be untouched. If you have trialled/demo'd Jira, JSD…
-
Ah, I think you're talking about "ranking" now, not columns Ranking sub-tasks outside their parent issue is nonsense, so you can't do it when they've been divorced from the parents.
-
It's hard to say, as the database custom fields are not Atlassian fields, and hence have their own behaviours. I suspect it's the field trying to read the database for many issues.
-
Columns on boards have nothing to do with priority, they are groups of status. If you can't move an issue from one status to another (i.e. into another column on a board), then the workflow is set up to disallow it. Have a look at the workflow for the sub-task type, and check what it allows from the current status. If the…
-
That suggests someone has changed your board filter to exclude "done" issues.
-
First, set up a issue security scheme that does what you need (one level for "import", with a rule "only group import_department") Second, use the ScriptRunner built-in script (see https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html#_set_issue_security ). That wasn't built in until recently.
-
An issue can be in many sprints. Aron's suggestion on the pivot will work because of that.
-
It's still valid, for the listed field types. In your case, do NOT ignore the warning that's not well highlighted in the middle. "When moving from a Multi Select List to a Select List, you have to make sure that only one item is selected for each multi select list." If you get that wrong, you can end up with an unusable…
-
I think this is the key point: when trying curl -v using external/redirected ip says: * Connection timed out That's telling me that your external/redirected ip is configured incorrectly on your network. A firewall would give you a flat "connection refused", so there's either a routing or dns problem here.
-
The whole point of Jira Software is that it provides Scrum and Kanban boards. Can you explain what you mean by "agility boards"? There's nothing like that in Beta on the Cloud instances I've got access to.
-
Remove the field from the "edit" screen for the issue type. That prevents users changing it (it looks like a calculated field to me)
-
Jira is an issue tracker, not a "host". I'm not sure what you are thinking about here. But the download is simple - see https://confluence.atlassian.com/adminjiracloud/exporting-issues-776636787.html
-
You can name the field in the notification scheme for the project. When trying to do approvals without Service Desk, you probably want to move the "approve" into the workflow, so that it becomes a transition. If you want to do it in other ways (like the approvers commenting or ticking boxes), then you will need add-ons.
-
I know of two ways to replicate it on a Mac. 1. Get the permissions wrong by running it as the wrong user, or by having the wrong permissions on the installation directory. Best option is mentioned in the docs (the last time I followed them anyway). Install while logged in as an admin, but not start the service…
-
The multi-user-picker custom field is probably where you want to start here. Although I'd strongly recommend looking at add-ons to provide things like setting i automatically and building clever workflow conditions and post-functions to use it more effectively (some of them are free)
-
Possibly. I've seen databases well documented in Confluence, but I'd like you to explain "save database tables like a data dictionary" - what are they saving (text? tables? sql to create tables?) and what are they trying to achieve by doing this?
-
The cause of the problem remains the permissions on the files. It's a known problem when people don't follow the installation guide.
-
I think your installation is effectively broken because you've done partial roll-backs and then triggered upgrades against mismatched data-sets. I'm not sure what you've been reading on Atlassian's docs, but it's not got you going in the right direction. When you roll-back, you should roll-back *everything*, not bits of…
-
IF you have access to he Jira source code, this gadget is in it, and you can pretty much take 99% of it and compile it into a gadget with a more suitable colour regime.
-
You'll need to check the database logs to see why it is refusing access.
-
Examples I could give wouldn't help you - they'd look the same (just as inscrutable) as the templates you are reading. You need to understand the basics of html (I find https://www.w3schools.com/html/default.asp handy) and the templates - http://velocity.apache.org/engine/1.7/user-guide.html
-
3 is a very very bad idea - it's not just customfield tables. Caches and counter tables matter as well. There is another trick - create a spreadsheet with one line per option you want to add, and two columns (the second can be just a duplicate of the first!) Import it into a temporary project that has your field in it,…
-
I wouldn't do it with Javascript, that way madness lies. Use a proper field and a bit of code to change the value. What do you have in the way of scripting add-ons?
-
The front end error is too sanitised to tell us much. What do the logs say?
-
Yes, many times. HTML is more complex to generate, and it's not tolerant of errors - it has to be well-formed or your changes can be totally invisible. But you've hit the right files and docs for it.
-
The docs tell you "how", not "why". If you want the tight integration, and all your users collaborating in one place, then install them together. If you want silos or data segregation, install them separately.
-
You can't do it without add-ons. There are a lot of add-ons in the marketplace that enable it though
-
Not that I know of, Community is totally separate non-Atlassian software. You're right about Community Forums, you should be a Confluence user to use it, but you could use it in public, as long as you're careful with automatic signups (spam...)