Comments
-
For server, the obvious one is ScriptRunner, which can pick up the "project created" event in a listener.
-
1) Yes, if you are an academic organisation. Government organisations are usually not eligible though, academic licences are specifically for educational use. 2) You should buy with the same account, it is far easier to handle, because you'll be using the same server ids and SEN. I don't know what you mean by "additional…
-
Edit the workflow, look at the status on the workflow, there is a properties panel
-
You can't. Users without admin can only use "project import" in their projects
-
Go to the board, hit board-config and go to "columns", where you can map status to columns
-
It is one thing it can be used for. How are you storing "Test ID" in Jira? "Defect number" is easy - any report you choose can include the issue ID and you can jump to that via URL or quicksearch by simply using it (or key = abc-123 in a search)
-
>t looks like the Edit permission on issue type button has been removed or moved. I am sorry, but that sentence throws a load of Jira-related words at us which do not make any sense when we try to join them up. In Jira-speak: * An edit permission means "I can edit the issue" * "issue type button" does not make sense, there…
-
My best guess is that you have chosen a filter that is not shared with your users. Check who the filter and board is shared with.
-
You will need to explain what a "script number" is, and possibly what a "defect" means to you in Jira terms.
-
Connected, yes, but I think you need to define what you want from a connection before we can tell you a lot more than "yes"
-
I'm afraid validators are the answer to this one. You could try injected javascript (don't), or behaviours, but they're both by-passable, only work in some places, and hence prone to failure. Validators is the only way to do it.
-
It sounds like you might be looking at a "Core" board, while reading the docs for a Software installation. Core boards are very simple and don't have any config, they just follow your workflow. Add status to your workflows, and more columns will appear for them. I don't know if you have Jira Software installed. If you do,…
-
You usually see other problems like broken default pages and macros when the base url is wrong. The symptoms are however, exactly what you get from a non-functional Synchrony - everything works bar create and edit. You can do a simple test here - go to Admin -> Collaborative editing. Turn off collaborative editing, then…
-
Are you sure those are creation dates? There's not quite enough in the screen grab to be sure. Could you check the system date and time on the Jira server is correct?
-
Go to your my.atlassian.com account and find the renewed licence. It will have a key with it. Check that it has the correct expiry date in the description, copy the key, then go back to you first screen-shot and click the pencil to paste it in over the existing licence.
-
Not really missing anything. Jira will display the priority (and some other system fields) if they have data, whether they are on your view screens or not. In this case, even though you don't use the system Priority, this issue has somehow had one applied, so Jira shows it. The usual culprits are (unusually) an admin…
-
I'm not aware of any free ones that have that function, I'm sorry.
-
Ah, sorry, my answer crossed with this. There's no way to do this off-the-shelf, you need different workflows.
-
The create transition in a workflow can only have one end state, you can't change that. So you'd need a different workflow and issue type for each different starting status in your system. However, if you're happy with add-ons, there is a way to do this. Several add-ons provide "fast track transitions". These can pick up…
-
There's a band I didn't see the first time round, but they did a tour about 10 years ago and ended up at a festival along with a load of other bands I wanted to see. So, we went. The main band came on stage and were fantastic, but the first thing Chrissy said to me was "Eh? They're old men!". Given that their most famous…
-
That is correct. You can't inject CSS into Cloud systems.
-
The permission is there specifically to block code and users from deleting stuff!
-
They've been removed from SR, as they were too limited in what they could do. They could catch ordinary edits, and bulk changes, but if you changed issues in Jira Software, Portfolio or Service Desk, the structure of Jira's code meant there was no way to put validators in. Behaviours might be able to help you a bit though,…
-
Sorry, missed the domain thing. You'll need to change both sides of the proxy. A proxy says "When users land on this part of a site, serve up content from those servers over there". I assumed, wrongly, that it was only the Atlassian servers moving, so you'd only have to change the proxy to point at "those servers over…
-
Are you changing the database at all? If not, then the easiest route for all the applications is * Install an identical version of the application on the new machine * Get each one working with an empty MS-SQL database, just so you know they work before the data goes in * Change the proxy settings to point to the new…
-
I suspect that's the project type and possibly who your user is. The top one is from a Service Desk project where you have customers as end users, and Agents to talk to them. The bottom shot is from a non-Service Desk project, which customers have nothing to do with directly and can't see anything to do with it.
-
You can only convert projects to Software types if you have the Jira Software application installed in your Jira. You could reconfigure the project to behave much like a Software project (change workflow, different fields and screens etc), but you would not get any of the Software features from it.
-
The context menu helps me, although I'm not sure it is for everyone's taste. A right click on an issue (or set of selected issues) in the backlog gives us options like "move to top of backlog" and "move into first sprint"
-
Then it will pop up when you use that transition. The transition screens are very simple and non-conditional. If you don't have one, the transition is instant, if you do have a screen, the user sees it, regardless. Have you checked that you are looking at the right workflow and that you have published your draft?
-
Atlassian have stopped people adding bugs to their Jira because there were far too many duplicates and noise. They now ask you to raise them through the Service Desk so they can triage and de-duplicate. See https://support.atlassian.com/contact