Comments
-
I am very sorry, but "when I record the third one the pirmera and second codes are eliminated in automatic" is not explaining it for me.
-
It's not the "new design". Cloud has never allowed custom html.
-
Ok, that is a list of custom fields defined as scripted. What does "it was automatically deleted" mean?
-
It's a 6 year old video, I think you're wasting your time. Try following the documentation for installing on Linux, Macs are so close to it, the only thing you need to think about is that the file system layout on a Mac is a bit different.
-
Do you mean you want to be raising requests from the body of mail, or you want to echo parts of the request in outgoing mails? (If outgoing, which mails, and what body?)
-
I am sorry, but this does not make enough sense for me to work out what you are doing, what happens or what you are expecting. Some screenshots might help?
-
No, it's not that simple. It checks view access. Which is NOT the same as "person in the project".
-
But what? You might as well be saying "I want to report on my cat" - you're not telling us anything we can work with.
-
I tend to use Exalate and EazyBI, as they understand the data model for you. Hopefully, https://developer.atlassian.com/server/jira/platform/database-schema/ will put you right off the idea of using the database. Yes, REST is far easier - you can use JQL to run queries and get back single JSON record for each issue with…
-
Please, don't. Jira's database is a data store, not a reporting enabled thing. SQL is the single worst possible way to report on Jira. Please, get one of the reporting add-ons, get a scripting add-on, or pull data over REST. That said - try customfieldvalue if you must. You'll have great "fun" working out the rest of the…
-
No, it does not. It checks if a user has view issue, and create issue. Project "users" can be a lot more complex than that. Those are relatively simple checks, optimised, nothing to do with other users, and are absolutely not "is user on project" checks.
-
It's the "issue security scheme" - set one of those up, add "levels", say who can see each level, then you can set the level on the issues after you apply the scheme to the project (the only permission involved is the users setting levels need the "set issue security" permission)
-
So not between two projects, but involving issues from different projects. When you try to edit issues from many projects (or even of different types), Jira can only work with fields that are available to all the issues you are trying to edit.
-
What do you mean "bulk change between two different projects"?
-
There are search engines you know? They tend to report https://confluence.atlassian.com/adminjiraserver/migrating-jira-applications-to-another-server-938846962.html pretty much instantly.
-
Jira won't do that off-the-shelf, you would have to hack something. Three possibilities are: 1. They identified the module that provides the panel and disabled it. I'm not sure this is entirely possible, but I would take a rummage through the system add-ons to see if anything is disabled 2. Javascript bodge - check the…
-
You can't. It's not changed, an issue will only show in the first swimlane that selects it.
-
Both of them do!
-
I'm afraid you need add-ons to do this.
-
No, the best you can do is include the component field in your displays and reports. Or, if the component really is critical to you, then consider promoting them, so that projects are what you used to use as components.
-
I'm afraid that is a non-starter. Working out "who is in my project" becomes exponentially difficult because of Jira's flexibility, and, quite often, people are using mentions because they want to draw in someone who is not "in the project". I would like something that skips groups and uses its own rules. I should be able…
-
What does the application log say it is doing? <confluence home>/logs/atlassian-confluence.log (and a look at other files in there)
-
2 and 5 won't happen. If you want 2, then use an external directory which allows for delegation, and 5 is felt to be complex and confusing. It might sometimes to appear to be easier to lock people out than let them in, but when you have both in play, it's not only hard to code for, but people really don't get it and…
-
This warning you're getting is because it failed start up (probably because your installation mismatched the database), but restarting has fixed it and it's now working. You need to have a good look at the logs to work out what is going on.
-
You will need to make the space anonymously accessible to the whole world, and then restrict the pages you do not want the world to be able to see. The best way to do this is: Global permissions: Allow anonymous access Space: Anonymous access Top level Page 1: No restrictions Top level Page 2: Restricted to the login group…
-
"I want to report" or asking for bar and line charts doesn't really define anything. Dashboards are what I usually reach for when "reporting", because we can define them to take specific data sets for a group of users and choose many different ways of representing the data. Dashboards are mostly driven by saved filters,…
-
Do NOT do that. You can not run two Confluences against one database (Unless we're talking Data Centre, but that's a different case, and it wouldn't Even if you take QA offline first, then it will let you start Production, but it's going to go wrong in interesting ways (fixable, but you'll have to fix it again when you…
-
Ricard would not have lead you to ScriptRunner if it were. You need code to do this, there is non for it in plain Jira, so you need an add-on to provide it. Off-the-shelf, you could force your humans a little bit. Put a "workflow property" on the to-do status that says "can not log work", then they'll be forced to move to…
-
What "reports" do you want?
-
Yep, lots. Especially when cleaning poorly curated Jira systems. You will need to select an issue type to move all the existing hot-fixes to. This may vary by team, so you might have to do it a project at a time. If everyone is happy with the same target issue type, admin -> issue types -> delete will walk you through it…