Comments
-
The board filter defines what goes on the board, the quick filters hide stuff to allow you to drill-down into larger lists. There's nothing to arbitrarily use a third unrelated filter.
-
Roles are global containers, they exist across all projects automatically, you don't add them to projects at all. If a project exists, it has all the roles on the list.
-
Have a look in Admin -> Roles and check who is set up in the "default" for each
-
Scrum (and Kanban) boards are based on a filter. You'll need to edit that and add your new clauses to it.
-
No. And you shouldn't ever be connecting to a Jira database on any system. Apart from some data related to bug fixing, SQL should not be used with Atlassian systems. It is the worst possible way to report on Atlassian data, and you cannot write to an active system.
-
You would need to rewrite most of the "view issue" code in Jira to do this, and it will be removing useful information from the user's view, as well as rendering you unsupported and making upgrades harder. I would invest in training them better, not hacking a tool.
-
Don't attach the files in the first place. Removing that view link is simply a downgrade that won't stop your users opening the files. If you want to stop them grabbing the files, then the only safe way to stop them is to not put the files there to be used.
-
You will need to write an add-on to provide a whole new set of screens to repeat the functionality available with bulk-edit. This is "re-inventing the wheel". Please go back to your users and tell them "Jira already does all of this, but it's in a slightly different format to what you are asking for". IF they insist on…
-
Depends on the backups you were taking if you want the (possibly easier) route. If you were allowing it to do the nightly xml export, then you could simply import one of those into a new empty Confluence build. Look on the recovered disk under <confluence home>/exports You might also be able to simply copy the installation…
-
No, that's absolutely not true. The error message is "something has gone wrong". You simply do not know what without reading the logs. I'm glad you've fixed it by deleting data that's causing it, but it was clearly NOT fixed by the bug fix in JSD.
-
Ok, that's fine, it should be the same.Do you have Oracle Java 1.8 installed on this machine? Also, could a virus scanner be blocking?If it's not those, then all I can do is point at your download - I can download 6.3.2 and load it on to Windows 8 (I don't have a 7 to hand), which implies the download is fine, but your…
-
If you follow the "add existing", you should land on a screen that includes an "add new workflow" option.
-
There are many reasons this error could be occurring. You need to take a look at the log files at the time when one happens.
-
Did you adjust the sequence table as well?
-
Yes, you can. You do need to create every resolution you want to use globally. But, you can use "workflow properties" to limit the list available to an issue type at any point in its workflow. (As you can do workflows per issue type and project, this is "resolutions by project). It is not nice to build and maintain though,…
-
>I do not know the search column field where rejected can be filtered. Nor do we. You have not explained how this data is input into Jira, so we can't tell you where to find it or how to search for it. How are you defining "validity of Jiras"? How are you recording "rejected due to defect"?
-
https://confluence.atlassian.com/jiracoreserver073/editing-multiple-issues-at-the-same-time-861257342.html shows the options for bulk edit. They've not changed much across the various version 7 releases, or with the three Jira applications.
-
Please, tell them that deletion is a stupid thing to do in Jira. Then, at least, when they do the stupid thing, you can tell them not to try to waste your time "getting it back", it's their own fault and they should have listened.
-
That could be done from the issue navigator's "bulk edit" function (if you do the bad thing of letting them delete)
-
Duplicate of https://community.atlassian.com/t5/Jira-questions/How-do-I-implement-view-that-shows-user-tasks-list/qaq-p/676029
-
* Use the "assigned to me" gadget on a dashboard (it's usually on the system default one that people use when they first log in) * Get the users to use "issue search", and "assignee = currentUser()" * Get the users who are interested in single projects to use the project issue summaries. * Similarly, if they're using…
-
This is a broken requirement really. Issue types should change rarely, when you realise there's a mistake, or an over/under-estimate. They should never be part of a process. Changing issue type in Jira is not a simple process, you have to go through a series of checks to make sure it is not going to break anything, and…
-
Correct. The types are written in the code for the templates, there is no way to change them easily. "Have to hack" is my short-hand for "write some code (probably based on existing code) that will do what you need"
-
And you've downloaded a 32 bit SDK?
-
The project creation templates are not configurable that way. They're actually small add-ons that tell Jira how to build a project. To change the issue types they try to create, you'd have to hack those add-ons (or, better, copy them, and adjust them to make your own versions, then disable the system ones)
-
You allow them access to the space. Otherwise they can't see anything within it. Then you make sure there are two types of top-level in the space, one that is open to all, and contains your shared pages, and the second which is restricted, with view locked down to your internal users.
-
No, the limit for Cloud is currently 2,000 users. Atlassian are working on increasing that, but I doubt you'll see the limit raised until towards the end of 2018. I would look at 3rd party hosting instead - there are plenty of Atlassian solution partners and standard hosting providers who will run large Atlassian systems…
-
There are a couple of requests in Atlassian's Jira for it, but very little activity, suggesting it's not a common need. Simple formatting is enough for most Jira users, although I've seen a couple of creative uses of Scripted fields to highlight things in issues.
-
This is a fairly generic error which is usually caused by a bug, often in an add-on or when a specific set of circumstances have been set up. We'll need to see more of the log to see what the root cause might be. It would also be good to see what conditions, validators and post-functions you have on the "close issue"…
-
Quick filters will only allow you to add them if the JQL given is valid. The red squiggly underline in your JQL box is telling you that there is something wrong in your filter, and so it's not going to save it. You need to correct that filter, giving valid JQL.