Comments
-
You've got most of it there, you've listed the defaults, apart from the last "Create shared objects" which is not granted to jira-users by default. The Jira Users permission is "these guys can log in", but it's slightly different on Cloud and Server, and Cloud won't show it to you in the same way.
-
Older versions took your value of "page name" out of your braces and used it to pre-populate the new page when clicked (obviously, existing page names link to the existing page)
-
The last version of the Community was based on "Confluence Questions" - a forum like add-on for Confluence. Questions is less forum-like than Community though (Community is based on Lithium now, which is not an Atlassian product) You probably should have a look at the Marketplace for forums. I only know of one -…
-
Confluence is effectively one of the "Applications" (not apps) that Atlassian talk about. The export from Cloud that Ben downloads regularly can be used to create other Cloud systems, and it can be used to build Server systems (you host them, rather than Atlassian, and the Application is slightly different), although that…
-
No (although they probably would be useful there too) You need the field to be on the issue screens. Go to the project, then admin, then work your way down the "issue type screen scheme" to identify which screens are in use, and add the field to them.
-
That's what I said, yes.
-
Not unless you upgrade one to a version that is not compatible with the other. You won't lose data from this, and it is repairable by bringing the other system up to a compatible version.
-
You need to have two workflows. One with a validator on the create transition that simply says "if user does not match a rule, return false" (I'd recommend you also return an error message for them). The other one does not need a validator. Use the one with the validator for most issues, and the other one for bugs.
-
There's no way to do this natively. You could try to find or write an add-on that provides the same field, but with a different layout (I've had no luck finding one), or you could try injecting javascript to re-arrange the screen, but that can be very painful.
-
Boards are not projects. Check who the board is shared with, and also that the same people have at least "browse project" in the projects it is displaying.
-
Projects don't have fields, so it's for the issue. When a value is changed via a script or behaviour, you will see it the next time you land on or refresh a page
-
Gabriel was using a "definition of done" field on issues. Do you have a "definition of done" field on issues, or are you talking about the definition of done that has been added to Jira software's boards recently?
-
There is no way to do it on Cloud. AS you say, you need to change or add some javascript. Which you can't do on Cloud.
-
What are you trying to achieve here, and what documentation are you following?
-
Did someone reconfigure your boards, or change the sprint data? Look at the issue history to see what changed on them (if anything)
-
Sprints and backlogs belong to boards, not projects. All you need to do here is create a new Scrum board that has a board filter like "Project in (ABC, DEF)" so it looks at both projects. So it can then attach a backlog and sprint to them in one go.
-
You'll need to re-engineer the core of Jira to allow it to "know" which customer gets what css.
-
You'd need to inject javascript into the menu headers to do that, the html macro won't help you.
-
The error message is from your application, not from Jira. I can't help you much with that, but if you could give us the actual error response from Jira, I can talk you through that.
-
Could you explain what is wrong here, or what you're trying to "fix"?
-
That's not goingto work with a cascading select. A select list needs a fixed set of data to work with, and values stored on issues must be on that list for it to work. So, "reflect the remaining budget" is a complete non-starter because you'd need code to destroy the data you'd been entering (if you wanted the field to…
-
If you are using PostGres, then you need to look at the database server, not a random file on your file system. Look in the system information page in Confluence to find out where the database is. Or, on the command line, <confluence home>/dbconfig.xml
-
The database drivers do not usually do domain based user names. Have you tried it with just svc_jira ?
-
Only "site admins" group? They don't usually get access to projects. However, if you can login as admin, and see a project, the next question is "what project is the HockeyApp looking for?"
-
A lot of people run them on the same database instance, without problems. It's fine to run them on local servers or on separate dedicated servers too. Let your hardware, backup regime and licencing determine the route - the applications just want their own place to store data. You just need to be sure that they do not…
-
Log into id.atlassian.com and click on "account settings"
-
It's calculated from the time of request creation to the point at which the issue behind the request takes a resolution (i.e. is closed or signed off by the requester) There's no "start" or "end", there's no data stored for it, it's calculated from those two points in the workflow. My best guess is that your issues are not…
-
Both. Depends on what you need. For resilience, data segregation, config separation, or hardware reasons, you could run them separately. Or, for better integration, with developers able to help out helpdesk agents inside a single service, run them together.
-
That;s not field configuration, that's screens. What you should do for screens, is create two. One for DAM, one for Photo. Then create two "screen schemes". One should use the DAM screen, and the other the Photo screen Third, create a single "issue type screen scheme". In there, you can say "For DAM, use the DAM screen…
-
Could you explain "do not respond"? Do they not appear on the drop down? Do they not insert when clicked? Does the config box come up but not render?