Comments
-
On the "glitchy" point, you're right. They make mistakes, bugs happen, but over the years, I've seen Atlassian move from upgrades being a massive undertaking to something you can do while snoozing through a film on a dull evening. (I did two last night in an hour-ish, the only problem being me leaving a spurious comment in…
-
Nope, your only way to do css in Jira now is hacking the core. Which is absolutely not recommended (nor supported).
-
Admin is irrelevant to project actions. Admin means you have admin rights, not "can arbitrarily do anything". You needed to be added to the developer role because the permission scheme has a rule that says "Move issue: Role (developer)".
-
Well, you can, sort of, via marketplace, if it's a Connect add-on. Is your "new custom field plugin" a Connect add-on? If it's not, then you'll need to start again and redevelop it as a Connect add-on if you want to use it in Cloud.
-
Yep, that's where the doc points to.
-
Jira can be a very good fit for that.
-
Go to administrate your project and look at the "users" section ("people" in some versions). This lists the roles you have globally. Click add, select the groups you want, then the roles you want to add them to in that project.
-
Your co-worker probably has the admin rights - they will need to check the permissions are set correctly and then grant you the membership of roles and groups to enable the access they want to allow you.
-
The best you can do is arrange the order of subtasks in the "issue type scheme". The drop-down will initially default to the first subtask issue type in the list, but then default to the last one the user selected thereafter.
-
It can't work with anonymous users, it would be useless. Imagine this case. You ask people to vote for opening a new dog park in your town. To do this, you ask them to anonymously post a piece of paper into a post-box. Great. But, you have no identification on the paper, so you have no way of knowing if each "vote" is by…
-
Why did you change the server.xml like that? It does not need changing away from the default if you are just running Jira on http://something:8080 (it does need changing for your port of 8050, but that's not mentioned in your question, so I guess it's working ok) That is however, the second place I'd look. If you click on…
-
Jira doesn't do that, as far as I can tell. Could you show us?
-
The board is just a view of your issues. It takes the filter and sorts them into columns by status (i.e. the status you map). Dragging issues between columns is a visualisation of transitions. The arrows in a workflow that allow you to move between status. If you can't drag an issue from one column to another, then either…
-
Because Jira is all about the issues, not the projects. Projects are for holding config for their issues and grouping them, not doing project management with properties. If you want project properties, your best bet is probably the "Profields" add-on (which also adds some handy project reporting stuff) The ability to set a…
-
You can't do this directly, and you need code to create the required linkages. To do this on a simple basis: * Create each component you need * Create a group for each component, and add your users to it * Create an "issue security scheme" and apply it to the project * Create levels inside that security scheme, one for…
-
It can't work by definition - the excerpt is displaying the original content, so if you change it, you're changing the source, which then gets re-rendered in the pages that include it, because you've altered it.
-
Go to "board configuration -> columns". You can add, rearrange and remove columns in there, and then put your various status into the right columns.
-
Most of the documentation I read or even write has no use for menus, check boxes and so-on. Formatting, absolutely, but that's there. (Table filters - sometimes). Usually people asking for that need forms, which is not what wikis are for. Atlassian are doing stuff around gauging usefulness, but from what I hear, the…
-
It might, with a bit of code, but it can get complex quickly. "Move" is not a trivial thing to do in Jira as it needs to check all the settings on the project and issue to find out where they clash, and ask the user for more information if necessary. All of that needs to be replicated by your code. In general, a desire to…
-
One of your board admins has changed the "estimation statistic" from "Time tracking" to "Story points", and/or removed the "time tracking" field from your "edit" screen.
-
Anonymous means "not logged in", not "logged in, but not named in permissions". It's counter-intuitive, but technically right. Try logging out and visiting the page again.
-
Have you mapped any status into your new columns? Columns without status are useless, so Jira hides them
-
No, sub-tasks are enabled at a project level and are not restricted by their parent issue type.
-
Your description of "global" is spot-on. I have one Atlassian account which has access to all sorts of bits of Atlassian sites (I work for a partner, so I have access to partner related stuff, as well as the stuff you can see on my.atlassian.com and so-on), and 25-30 Jira and Confluence Cloud instances that are all client…
-
There is a non-obvious quirk with "anonymous" that you may have run into. There's two possible states for a human interacting with Confluence (or Jira for that matter). * I am logged in: The system knows who I am, and will check all my actions against all the permissions for the things I try to do * I am non logged in: I…
-
From what I've seen, very few people have problems with getting add-ons. I would say that I don't think I've ever seen two sites with the same set of add-ons. Almost everyone has some, but the sheer range of them makes me question what you call "basic functionality". If Atlassian adopted everything that different people…
-
Again, you do NOT do this. If you make it editable, your users will corrupt your data. Please read the conversation linked to, I don't want to repeat it again.
-
As Joe says, "Jira does not do field level security". You can either edit an issue - all of it, or not. The only (native) workaround is to remove your AAA, BBB etc fields from edit so that no-one can edit them, and then create a transition that goes through a screen with one of them on it, protected by a condition. (So…
-
Excellent. This is very much a case of fitting the software to best fit your needs, not a "there's one way to do everything with JSD". The community is always interested in case studies and examples of where people have managed to make it work really well, and clever tricks played (and the odd precautionary horror story…
-
That's a status, not a transition.