Comments
-
I'm not sure what you are looking for when you say "enabling search box" - there's been one on the boards for so long I can't remember what version it arrived in. What do you think you are missing and what version of Jira are you on?
-
No. A sprint represents a list of things you have committed to doing for your product owners and users. Those are stories (albeit there's plenty of space for calling them different things) A sub-task is a part of a story. It is not something you commit to in itself because it's irrelevant outside its own story. So…
-
That's what we said before.
-
This is one of those computing terms which have an annoying clash. Directory could be an element in a list of file directories, or a directory of users. These are two very different things. The user folders which you have changed the permissions of are file directories, and not what the error is about. The error is trying…
-
How are you handling test cases in Jira? Natively, Jira has issues and those are not test-cases. Some of us try to rig something up so that certain issues look like test cases, but most of us use Test Management Apps. So the question is are you using a native setup, or one of the Test Management Apps? If it's native, then…
-
Workflows are associated with projects via the "workflow scheme". See https://confluence.atlassian.com/adminjiraserver/working-with-workflows-938847362.html
-
It looks to me like "cust-demo" is not a group listed in the role of "Service Desk Customer - Portal Access" for that project. The code is returning three other groups and a couple of users. My best guess is that you're looking in the wrong place - cust-demo being the group you have named in global permissions as users…
-
The error is nothing to do with the name of the mount point or directory. The problem is the file system. Jira does not work if you put certain parts of it on an NFS file share. You need to move (part of) the home directory off NFS type disks and onto fast local storage rather than a share. Try the command "mount" on the…
-
See https://confluence.atlassian.com/cloud/data-storage-faq-873871367.html
-
It's because Jira has a lot more power than Trello, with ranges of different (and differentiated, rather than just a blob of text) data, which has a downside that you have to be a bit more "clever" with the searches to cover all the places you might mean. The quick search field applies a guess at what you might mean, and…
-
An issue lives in a single project. If you break up your development into those three parts by doing it by project, you are going to have to duplicate each issue into each project separately. Consider either using components, a custom field or sub-tasks to break up a story into each element instead. This does have the…
-
It sounds to me like you are not editing the copy, but working on the original, which is still associated to all the projects. You do not mention if you have tried to put this workflow into a workflow scheme and associated it with your project. But I suspect you have not. So go to the list of workflows and look towards the…
-
Your program will need to read the Jira system (using the same API it is using to write) to look for whatever it is that you do not want to duplicate.
-
No. The files exported by each App are totally different to the other one. They are not in the slightest bit compatible
-
There are two things you will need to think about: If you want data to go from Jira to Nineleaps, you would probably want to use triggers and post-functions to post data as things happen in Jira. Without knowing what remote calls Nineleaps might have, we can't tell you a lot more than that. In the opposite direction, you…
-
You would have to find or write a script or automation to do this.
-
The sprint report is generated when you visit it, the data for it is not directly in the database. You'll need to combine the sprint field value(s) with the change history of each issue to work out most of what the report shows.
-
The comments and logs are still there, but your removal of the group means that they can't be seen. Groups are not keyed off their name, but off an ID, even though you've added one with the same name, it's not going to replace the old one because the new group has a new id. The only things I can think of to "fix" this is a…
-
You will need to read the log files to find out why it is not starting.
-
Yes they do. Just flip the "include subtasks" flag.
-
Size of attachment is only capped by a setting in Admin -> Attachments. There's no cap on number of attachments, and the overall size is only limited by your disk space. Attachments will remain until you delete them or the issues they are attached to.
-
No, you have to use it on a single base url. You cannot point two servers at one database unless you have Data Center. But DC still only has one base url.
-
Correct. You've deleted it. The DB won't have anything because you deleted the rows representing the group.
-
So when you scroll down the list of fields, do you see "Change Story - Mat & Story - Code Review"? They are sorted alphabetically, after the system fields at the top.
-
Start at https://confluence.atlassian.com/adminjiraserver/working-with-workflows-938847362.html But if you have Service Desk, that has some approval workflows predefined for templates already.
-
You need to get an existing administrator (or user administrator if your directory is external) to add you to the administrator group.
-
Yes, in fact only on Server. It's the only recommended way to do extra tables in the database.
-
No, the group has gone, along with all the settings that relied on it.
-
Create a status as normal, either by creating it via admin -> status, or editing the workflow. Then map it into the column via "board configuration"
-
It's no longer able to connect to the database. You'll need to check permissions, logins etc.