Comments
-
Comments on create don't make a lot of sense - if the creator has useful things to say about what they're writing, then they go into the description. A secondary "notes" box catches the cases where you want something specific or highly structured in the Description, but then putting it into a comment is totally…
-
Ahh, yes, that would be confusing! Backlog of backlog!
-
The button hasn't moved recently - it should be at the top of the backlog (but below existing sprints) on the right-hand side. If it's missing, could someone have revoked or changed your rights to manage the sprint?
-
There's some flexibility if you are happy to do scripting, but off-the-shelf, it'll happily read in Word (albeit individual pages) and simple text files. I've done a few imports with a "scrape existing site, run it through html2text to create one text file per page, run import" With scripting or add-ons, you get a lot more…
-
That's a pretty big structural problem. Turning off indexing is the worst thing you could possibly have done. You need to look into the performance issues, not render your systems useless by turning off bits of them.
-
A customer should see their own *requests*, but not the issues behind them. They are limited to the portal, and the issues they (or their organisation) raise. You say you've had your customer use "create an issue" - do you mean that they did it in plain JIRA, or do you mean they raised a request via a portal?
-
Nope. There's a big clue in the description though - the last line tells you to check the logs - they will tell you why it cannot start up. Read them, and if it's a clear message, you should be able to fix it. If you're not sure what they're telling you, then add the details of what the log says here, and we can try to…
-
Use different names for the sprints, clarifying what they're for. The problem you've got is the underlying data is shared, so when you say "sprint 1" (version x) you're looking at the same items as you when you say "sprint 1" (version y), so JIRA has no way of knowing you mean two different things. Most of us will do…
-
You don't. If I have understood the question correctly, you are looking for a display like * col 1, col 2, col 3, col 4 * ------ * col 5, col 6, col 7, col 8 This would cause layout problems for almost every user of boards, and so Atlassian have not done this. Your only option is * col 1, col 2, col 3, col 4, col 5, col 6,…
-
Is there a way to export Assembla content to a standard format that Confluence might be able to read?
-
It's on the servers you put the application and database on. For Server and Data Centre installations, that is up to you - they're your servers. For Cloud installations, they all live in the US at the moment, although there are plans to build a second stack in Ireland.
-
This Stephan Bakker is (at least) a site admin for your site, and should show up in the list of users, so you should be able to identify them from that. And remove him if you're unsure of who he is. Atlassian people generally won't touch user accounts unless specifically asked to do so on a support request, and they use…
-
A service desk request is a layer that goes on top of a JIRA issue. The JIRA issues are usually more complex and detailed than the requests and have a lot more fields, with only a few shown to the customer making the requests. If you have configured the JIRA issue to have a mandatory field that must be filled in, then…
-
Use the REST interface to query JIRA for that information - see https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-query-issues as a starting point (lots more docs are in that tree, I just start with the tutorial because you can see how it works immediately from…
-
A new field add-on is the right approach, but it's not going to be a trivial "simple custom field" You will need to put a field on screen for capturing the incoming file somehow, which should be straightforward, as you'll just need to capture what the user says and call for their upload. You probably want to have a second…
-
The Developer community is currently built on Discourse, whereas I can confirm that Stephen is right about this being built on Lithium
-
I'm with Renjith on this. A requirement for "regular reindexing" is almost always masking a significant problem that you should be fixing. It's "plastering over the cracks" instead of "fixing the subsidence of the house"
-
A snippet of code is needed, but it's just a post-function to set the flag.
-
Ok, do you have a specific question? This is a good place to meet people, but you will generally find you want to start a discussion somehow.
-
Please, don't copy and paste answers from other places. Continue the conversation, over at https://community.atlassian.com/t5/JIRA-Core-discussions/How-to-take-Backups-of-JIRA-through-Netbackup/td-p/588308
-
Repeating the question does not clarify it. Please explain what you are trying to do with JIRA?
-
* Go to admin -> Backups * Click backup * Wait for the file to be generated * Click download when the link is given to you Sounds short, because it really is that simple.
-
See https://confluence.atlassian.com/cloudkb/pros-and-cons-of-cloud-vs-server-691011844.html
-
The technical answer is a simple "yes". JIRA doesn't actually care what the issue type is, so you can put Story points on issues, features, bugs, tasks, penguins, etc. As long as the issue type is at the same level as "Stories", it's fine. (Don't put them on sub-tasks, that way lies madness) The real world answer is pretty…
-
If you have the application links correct, then you can highlight lines or bullet points in Confluence, hover until the popup appears, then hit the JIRA logo - it'll turn each line or bullet into a JIRA issue, leaving the user in Confluence.
-
Ignore my last answer, just realised a tag has been added that makes it not relevant.
-
The fields a user chooses to select from ones available is up to them. If they choose to deselect a mandatory field, that's up to them. Think of it this way: I have set a preference that says "Show field X, hide Y and Z". This is a global setting for all my screens, because I don't care about Y and Z. We have projects A, B…
-
That IS the "simple" process. I wouldn't have posted an unnecessarily complex process, it would not be a good answer.
-
That looks right to me. Not tested it, but it should do it.
-
First, separate out "upgrade" from "change database". You don't really want to do them at the same time. You should always test these things, and if it all goes well, there is no problem booking one block of time to do both, but always do it one step at a time. See…