Comments
-
Not convert, without fiddling with some system files, but you could write a web-fragment plugin that could add it as a button, I believe.
-
No, you'll absolutely need a plugin, and in fact, I'm not sure you can even write one to trigger it - you probably need to alter core code. I'd also forget the idea of moving an issue during a transtion - it's not in a state where you want to trigger the move as the "wizard" will use the old values you've got on it.
-
Um, repeating the phrase does not help us understand the meaning. Do you mean the .vm files that are used to generate a page for the user? As they're called templates. Or the searcher type? Or something else?
-
What do you mean by "search template"? The only thing I can think of is the .vm that defines what a user sees when you write a "searcher"?
-
Because you could drop the issue type at any point in the search editing you're doing. If you restrict it to just the fields for the current issue type, what do you do when the user constructs a query that might start to include the field? Simple answer is that you have two choices - offer everything so you can be…
-
Fields show in tabs when you add them to a tab within a screen. Doesn't matter what the type of field is. "We had to select ALL to view it" makes sense though - your user had previously decided to hide the field, so Jira then hides it. Then, I suspect that you had put it on a tab with nothing else, so Jira hid the tab as…
-
Tabs on screens are controlled by the screen-schemes. Have you set these correctly on the project? Also, if there are no *valid* fields on a tab, it ends up hidden. So check that your custom fields on those tabs all have the right context for the project and issue type. Also check the field configuration allows for the…
-
You'll need to explain what you want from a "variation report", it's far too vague a term, even if you have a context like "project management"
-
No. You can't change the URL directly. You have to trial and buy a new system on a new URL, then, if you want to keep any data from the old trial, export it, adn import it into the new system. Then you can simply let the old trial lapse.
-
That's the wrong way around really. You "add" (or better "associate") a scheme with a project so that the project uses it. As an admin, go to the project admin screen, look for the issue type section and click on the selection that allows you to change to another one.
-
You'd mess up the time-tracking if you altered the way that field works, and you'd need to be hacking the core code in JIRA. You've got a couple of options: You could create a new field (date/time) and use a post-function to populate it as you move through the workflow. There's no built-in function for that, but there are…
-
See https://confluence.atlassian.com/cloud/data-storage-faq-744721620.html
-
You'll need to write a plugin to provide that. Jira doesn't have any code that could support this natively, so your options would be 1. A plugin that provides a single field which can handle both lists and their interaction, with code to store and retrieve data using some of the existing data structures 2. Javascript that…
-
Confluence isn't a file store or document repository, it only really handles small-ish attachments. For 4Gb files, you probably want to be looking at a different system that is designed for storign and transferring large files. Most places I've worked have implemented systems that look pretty much like file shares, and…
-
They don't really "break it down" anywhere to be honest (I've just had a look around and they do say what you're entitled to in several places, but there's no actual list in one place) I suspect it's because there is not really much to list. Your licence entitles you to any version of the software released before the end…
-
Hmm. That's an odd one, because if the server can reach the "corp" directory, it shouldn't matter what the client machine is doing.There has to be something broken on the client machine, but I can't for the life of me work out what - the client should talk to JIRA, JIRA to your directory.Could you try a different browser…
-
It's quite hard to guess with "I can't log in" - what is the symptom here? Do you get to the server at all, or do you mean you can't reach it? What error messages do you get?
-
Have you installed the JIRA Toolkit add-on in production? (The main question I'm reaching for here is "what are the differences between Test and Prod - but the most likely explanation is that you're missing the Toolkit on Prod)
-
Could you explain what this has to do with Atlassian applications?
-
No. For the third time, IT IS ALREADY OPTIONAL. But, if you put it on a screen, it is defaulted and cannot be blanked out. As Randy has said you should only ever put it on issue-view and transition screens when you want the user to enter it.
-
As I already said, it's optional already (and you can't make it required) As Randy has said you should only ever put it on issue-view and transition screens when you want the user to enter it.
-
All JIRA's have and use the Resolution field. It's a system field, built in, and it's quite important as it is the field that tells the whole of JIRA if an issue is done or not. It is always optional. But, if you put it on a screen, it is defaulted and cannot be blanked out.
-
Well, you could easily go "old school" - find or write a plugin that provides either a post-function (or listener if you need one that works for "edit" and not just after workflow transtions). Your code can generate whatever calls you need, in any format you can code for then!
-
No, you can't - the configuration is pretty much fixed as "a valid JSON representation of some issue data". You'll need to make the webservice understand that, or you're into modifying Jira source code to change the output of a web hook.
-
A watcher is a user who has chosen to watch the issue. An attendee, is, well, probably a user who you name in a custom field called attendee. But we don't know what you've configured to make it available. (JIRA's built-in user fields are Reporter, Watchers and Assignee, I don't know where your attendee has come from)
-
Duplicate of https://answers.atlassian.com/questions/38514337
-
You need to change ALL of your permission schemes to grant it to that user. I'd recommend using a group though, so next time you can just add the user to the group and be done with it.
-
"new and fresh capabilities" would include "adding text fields to versions". I imagine you can do that with a plugin, but I've not tried it, or seen it done in a simple plugin. Yet.
-
Look for atlassian-jira.log in the logs directory under JIRA "home" (have a look at admin -> system information to get an exact path) You should find it's saying stuff like "unable to match this email with a JIRA account that has the right to create issues in the project... deleting it" If there's nothing obvious in there,…
-
It sounds like the board filter or column set up does not include the issues. First, check the board filter does not refer to any status - e.g. "Project = XYZ and Status in (open, in progress, held, done)". If it does, then you need to look at what status the issues are in after you change the workflow and check that it is…