Comments
-
Doesn't matter if it's "not an acceptable answer", it's still the right answer (unless there's something else we don't know about) Try the tests with completely new users, I suspect you'll find that while Beta probably is a new user, you've been changing settings for Alpha and that's what Alpha is inheriting.
-
Ahh, no, that's a built in feature - the later versions of Jira allow the users to hide fields they don't care about, on an individual basis. At some point, the user has changed their settings. That was going to be my next guess (but I wasn't that familiar with it and didn't recognise the wording, hence the guess at a…
-
That sounds like a plugin of some sort - could you explain further?
-
There are some fields that can only be set if you have the right permission. You mentioned assignee - that field will only be offered on create/edit screens if the current user has the "can assign issues to people" permission. You'll find reporter (can edit reporter), fix versions (needs resolve issue) and due date…
-
Sounds like she's been logged out! Start by asking her to leave JIRA in the browser, clear out cookies, close the browser, then re-start it and revisit JIRA - does that change anything?
-
It's the same rules as the old editor. "Regular page security" as you suggest.
-
No, the wiki markup has gone from 4.0 completely. Your only option is a downgrade at the moment. I've got a feeling a couple of people are looking at some form of wiki editors, but it's early days.
-
Sorry, I don't understand? To add an admin user, you add a user and add it to the admin group.
-
That won't work - you need admin rights to update the admin group. Updating the owner of a filter by any old user is probably not a good idea - if I've written a load of filters and used them in dashboards and reports, then I don't want other people arbitrarily taking my filters away and possibly breaking them for me. The…
-
Well, your plugin could add them to the administrators group, but I'd strongly recommend not doing this (as all of my Jira jobs in the last 9 years have started with "please clean up the mess made by having too many admins") Could you explain what you are actually trying to achieve in this plugin? I really don't think you…
-
You've used the Cloud tags, which suggest you're on Cloud. If that is true, you should raise this with https://support.atlassian.com as soon as possible. If you're not on Cloud, then you need to read the application logs to find out what has gone wrong and where.
-
Another reason not to use Cloud. User impersonation is a dreadful idea that really should be taken out and shot (unless every single action is logged and reported to the impersonated user)
-
What add-on are you using to enable the user switching?
-
It's not a bug, it's just a weakness in the design. A common one for all systems that allow for on-line editing. Some handle it better than others. (Confluence falls in the middle of the range for me. It's not great at handling it, but it's a lot better than most other options) Atlassian systems do not get patches, other…
-
Possibly, but Cloud does not support IE9, so it doesn't matter. You need to move to a supported browser.
-
I don't understand the problem. If you have a transition you want to hide on a step, then use a condition to hide it.
-
Place conditions on the transitions you want to hide, so that they are hidden when you don't want to see them. Use the and/or functions that Jeremy pointed at. See https://confluence.atlassian.com/jira/advanced-workflow-configuration-317196666.html#Advancedworkflowconfiguration-conditions
-
This is the same question as you asked yesterday and it's nonsense. You have many transitions because you have many transitions, not conditions. See https://answers.atlassian.com/questions/30939218. which has answers that explain your misunderstanding already (and Jeremy's answer for what you should set up)
-
No problem, I do exactly the same all the time when I'm sketching out JQLI do search in the future, but it's usually something like "due date in the next two weeks", but dates in the past do form the vast majority of everyone's searches in my experience!
-
I think you've got your relative dates wrong, if I am reading the question correctly. Might be easier to explain the clause: AND updated < 15d That means "updated date is before a date 15 days in the future ". I think you actually want: AND updated > -15d That means "updated after a date 15 days in the past" (Also, the…
-
What errors did the import give you for the issues that were not imported?
-
No problem, it's well buried in the middle of https://confluence.atlassian.com/jiracorecloud/working-with-boards-800712866.html#Workingwithboards-problem - I had to read it a couple of times to pick it up!
-
You wait. Issues are removed from the column once they've been there for 14 days.
-
I'd recommend checking that this isn't already logged at https://jira.atlassian.com/projects/BON/issues/BON-1974?filter=allopenissues and then raising it there if it isn't.
-
I've used simple derived custom fields to do this in the past (requires a bit of code - I've always done it with a really basic plugin, but I think it can be done with the script-runner addon as well)
-
You didn't used to have to re-index, but I've not tested that in 7.1. The reason is that the renderers only kick in when displaying the text - the underlying data is the same in the field, it's what's being drawn on screen that matters. Do the existing issues have wiki markup in their text field?
-
https://confluence.atlassian.com/display/JIRA/Supported+Platforms
-
I can't see anything more up-to-date than https://answers.atlassian.com/questions/28745/possible-connection-between-ca-clarity-and-jira-greenhopper It seems like Clarity have some stuff themselves, but I couldn't find it on their site.
-
The move process asks the minimum it can of the user. So, if the target issue type's workflow uses the same status the issue is currently in before the move, it won't ask you to change it because it can transfer it automatically. You've got two options I think * Write some code that can catch "issue moved" and do a "see…
-
Short answer is "no". The GUI has been changed to the new format, there is no code for the old format left. You can, of course, invest time in coding to change it back, but there's a lot of layout work and css to update, and you'll have to redo it on every upgrade.