Comments
-
This question is four years old, and things have moved on. Most of us can no longer create issues for most projects in JAC, as it's not the route Atlassian want us to use any more. Try https://support.atlassian.com/contact
-
You'll have the same structural problem in other systems. If a user doesn't identify themselves, there's no way a system can know what to hide or show them.
-
Ugh, I pity your users. On the bright side, more chance of extra work for me when we get asked to repair the mess you've made.
-
Really, you don't want to do this. But, if you insist on shooting yourself in the foot, there are four .jar files in your installation: atlassian-nav-links-plugin jira-issue-nav-components jira-issue-nav-plugin jira-projects-issue-navigator They will have those names, but with -<number>.jar on the end of them. Stop your…
-
Yes, there's an explanation of why in the boxes you have in your screenshots. Please read the messages there and follow the links given.
-
You don't need this "public" security level. It's making it more complicated because Jira has to distinguish between logged in and non-logged in users. Use "anyone" in the permission scheme to allow non-logged-in users access to everything in the project. This is your "public" access. Then, for any issues you want to hide,…
-
If a user does not log in, Jira cannot know who they are, and hence what to allow them access to. If you don't care that everyone will have access to everything, you can start using the "anyone" group in permissions, which will allow "anonymous access", which means people don't have to log in to see anything.
-
We're not support, we're a community of end users like yourself.
-
The only native way is to remove it from the edit screen. You can't disable in-line edit selectively. You can try something like Behaviours, which can remove it field-by-field, but a) don't, it's useful for users and b) it's easy to work around it
-
It sounds like it has lost connection to the database, or the database has been emptied or corrupted. Could you read the logs to see what went wrong?
-
Yes, I see that's a bit painful. Usually is when you inherit someone else's stuff (You wouldn't believe some of the rubbish I've had to unpick from inherited Jira and Confluence systems) >Much of the content that I wish to reuse is already located inside pages where the entire page is set inside an "Excerpt" I would want…
-
The user of "include" and "include excerpt" you describe here are pretty much the main reason the macros exist! It's a very good use for them. The only qualm is the "hidden" section. The include macros respect the privacy and page settings for their source, so you don't want to hide them. You almost certainly do want to…
-
Ahh, well spotted. Given your list of add-ons, the first line of my response was going to be "a broken script", although I was thinking more of a post-function than a validator (that's the usual way I get scripts wrong!) Scripts can be done in Jira with in-line boxes or by existing on the disk under a "scripts" directory…
-
I can't see one that goes beyond the standard 2-dimensional severity/probability combination. I think there's a market for a 3d version, but I don't know how large it might be. Sadly, that means I suspect you'd have to write one for yourself.
-
I've always used the command line to restart AWS stuff (and investigate the logs) - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html seems like one of the more recent guides. The partner search page works fine for me on Safari and Firefox, so I suspect there's something on your network or…
-
Best you can do with two separate instances is basic issue linking which won't provide updates on either end. The more clever stuff generally works because the Software and Service Desk applications are running on the same Core service. Synchronisation add-ons are the way to go if you must retain separate instances. I'll…
-
>think that the previous system admin just used the same permission scheme for all projects, thus it should not be an issue That's not true. What happens if the permission scheme says "manage projects: role (p-admin)"? A user might be in the role in project 1, but not in project 2. Same scheme, different user access. Two…
-
I can't line that up with anything Jira would do, unless your database had been damaged and what you really mean is the "error" was "you have no database set up, please run config to create one". Is that what has happened?
-
And it doesn't change the defaults in the fields, just updates the issue.
-
Ok, you've narrowed it down to your Bitbucket connection. I'd want to read the Bitbucket logs to look at why it's failing, but I still think you're going to find it's the connection hanging. "too many failed attempts" is the error in the code that occurs when Bitbucket logs many attempts to log in with either the wrong…
-
I'm afraid not, add-ons are licensed at the highest tier of the applications you have. 150 users puts you in the 101-200 tier, so you'll need to pay for Portfolio at the 200 user tier.
-
Igor points you to migration docs that point out all the other steps beyond the database (attachments, homer directory, re-indexing etc). You need to go through all of those.
-
You'll need to explain "gogs" in a bit more detail. But I think: * that you need "alphanumeric" in the last field in your screenshot, * I'd suggest that the "external issue tracker url" may be wrong, I suspect it should be the base url, not a specific project link. * The url format for a Jira issue is usually <base…
-
It's an opinion backed with many years of experience, which includes several times where I've been paid to identify and remove hacks that get rid of the assign option when someone has done it. But yes, we'll have to agree to differ.
-
This all smacks of a broken and misunderstood process where people are working on a "not my problem" basis instead of understanding what they are doing. The vast majority of Jira users simply don't have this problem. In fact, there was an option to remove the assign link back in Jira 3.something (if memory serves). It was…
-
These are vague statements that can't really lead us in any simple direction. "Reduce overhead for ticket management" is the least useful one for example - I'd go with * set up your Jira with simple, clear processes and * delegate all the work to the developer teams, and * consider Service Desk if you have Customer type…
-
Please, could you just give us the three filters I've asked for. We simply cannot answer the question (or confirm that it's a bug) without those details. We don't need screenshots, we just need the three JQL statements you are using.
-
I disagree again. There are many cases where you need to assign without transition, and where you need to transition without assign. In the overwhelming majority of systems, you'll find reasons for both. And your users just clicking "assign" and not moving things on screams that they don't really understand what they're…
-
No. There's a clue in the name "Portfolio for Jira" Portfolio is an add-on for Jira, it adds some data structures to an existing Jira, but the main data it works with is Jira issues (and projects, and users, and Software stuff if you have that, etc).
-
Go to a search, find the issues you want to export, then use the "export" button.