Comments
-
Ah, I see. Not sure what preprod is, but I can understand why the Atlassian stack is sometimes described incorrectly. My sales guys would tell me off if I didn't suggest you have a trial of Community Forums :-)
-
An older version of Jira used to prevent admins adding or renaming fields to have the same name as existing fields. You could work around it by doing imports and selecting "new fields", but generally it was really helpful in stopping admins doing bad things. It was really annoying when that was dropped and duplicates…
-
That would require code change in the core of Jira. It would also introduce an annoying inconsistency - when a user clicks on a field result, the search returned is for the field they've clicked on. Your spec would return a search that has nothing to do with the field they are clicking on.
-
No, but you might want to look at the "view tracker" add-on to capture the baseline usage information you'd need to start building your analysis on.
-
That is why I'm quite negative about it as well. There's no logical justification for it. A lot of stuff that looks useful but Atlassian decide not to do is justifiable for all sorts of reasons - bad practice, confusing for users, the coding would be huge for little benefit, it's an edge case most people don't need - all…
-
Could you explain "global shortcuts" and "references to missing or limited shortcut permissions "? The second question is asked because I don't believe Jira limits shortcuts in any way. I do know that it will ignore the use of a shortcut if you don't have permission to do what the shortcut does, but that is not limiting…
-
Much as I'm an Atlassian fan-boy, I do still see some of their failures past my free-t-shirt-and-beer haze. They have still not done anything to allow us to move issues between status in the same column. They've also closed most of the improvement/request/bug reports that cite it with a "won't fix" message one way or…
-
If it helps, a common structure I see is to split spaces into two root parts. You have a "public" page at the home level and a "private" one, restricted viewing to only your internal users. Internal users work in pages underneath the private one, and move (or copy, or use other duplication methods) pages that should go…
-
@Dalibor Selucky- I am sorry to have to be rude, but everything you've just said there is wrong. 1. Bubbles was never a Jira function, it was for Confluence 2. It was renamed to "Community forums" a few years ago (This is a good reason not to comment on 5 year old questions! It is out of date) 3. Community Forums is fully…
-
This is not how Confluence works. A licence gives a user the right to log in to Confluence. What they can do when they are logged in is up to the administrators and space owners and varies by space if you want. My Adaptavist account on our internal Confluence consumes a licence slot. I can log into our Confluence and edit…
-
The transitions between status have been defined that way by you or your admins. To answer "Why does it make you drag it into the transition name QA Notification 2 when the Status name is QA?" we need a few points: A workflow is a collection of status, with transitions that allow you to move an issue from one status to…
-
Look at a transition into the end status where you want them to select it On the transition panel, click "edit", then choose a "screen" for it. Make sure the screen you choose has "resolution" on it.
-
>Failed to create cache directory at: {} [stash_home/data/caches/scm/624] Suggests there's a problem creating directories. The two versions of Java suggest that there's a bug in the later version of Java as well. Your easiest option is probably "don't upgrade Java", but a better option would be to upgrade to a supported…
-
You can't fix it yourself, you need elevated rights you have to earn. The reason it was flagged is probably the massive stack trace in it - the spam filters don't like them much as they often appear to contain text that scores highly as spam, and on the most part, people don't need the trace. It's more tolerant in comments…
-
Hmm. Reading between the lines, I think you're in the wrong place. Unless "whm" is a name for your Jira system, I don't think you're talking about an Atlassian system. You'll need to explain what whm is to get much further here!
-
If it is a Core business board, then it will display a column for each status in the project's workflow. As you only have two columns, the workflow in there must only have two status. (Accessible status, ones with transitions into them)
-
Same answer really - you need to understand what Gogs expects and needs from you in order to configure it. We can't tell you a lot more than what I've said until you explain more about what you're looking for and what it needs.
-
Could you show us the base url in the settings? Could you also check that dns is resolving correctly on the server? When something on the command line tries to reach dev.prusa.3d.com does it land back on this server?
-
So what type of board do you think it is?
-
a) No, you can use a "developer" licence for a warm standby, but the licence lives in the database, so the replication would wipe it out. Just replacing it with a developer licence is easy though, and "disaster recovery" is specifically named as a valid use for developer licences. b) You would need to ensure the main…
-
Follow the standard installation instructions, but make sure for the second installation, you choose different locations, and edit the bitbucket.properties file to change the ports it uses.
-
Yes, if you make sure they are installed totally separately, the machine has the resources to do it, and you put them on different ports.
-
Check that you have "transition issue" permission in the project's permission scheme Open up the workflow in edit mode and check the "conditions" on the transition from identifié" to "annulée - do you match all of those?
-
This conversation is 3.5 years old, things have changed. I'd suggest you ask a new question, so more people see it, and tell us versions and what you're doing.
-
They don't exist. The database query tells us that. You'll need to amend the Structures you've got set up so that they reference existing filters, or remove the Structure.
-
Add the new admin account, then log in as it and remove the old one. All from the user management section.
-
The issue view automatically groups user and group fields into "people". Your options to move those over are: * Do not use user pickers for the fields * Find/write a custom field type that looks like a user picker, but does not tell Jira it is a user picker * Radical surgery to rearrange how Jira displays view screens The…
-
The "quick create subtask" link you've got only pops up a box with a standard set of fields. If you've made other fields in the subtasks mandatory, the user won't be able to use the quick subtask link to create one because the field won't be there for them. So it hides it.
-
The filters don't exist, that's probably what the warnings are. Could you tell us what the warnings actually are?
-
The answer is "no" really, because you can't have dangling attachments. Attachments belong to pages or issues. They can't exist outside them. Delete, move, rename a page or issue and the attachments go with it. Confluence I suppose does have one other layer - you could argue that something is "dangling" if there are no…