Comments
-
If you want a way to approach this without looking at the process, then you were close, but there is an easier way to work. Boards are for teams and select issues from anywhere, so instead of setting up projects as containers (and having the pain of having to move issues), create two boards. Board 1: For the developers,…
-
You might be able to do this with a quick filter for "not (issuetype in subTaskIssueTypes() and sprint in closedSprints() )"
-
You'll need a bit of code to do that, although I would question the usefulness as the url is already there in the browser. It is also easy to construct, as <base url>/browse/<issue key> I'd also recommend doing it as a scripted field rather than a post-function, as that's more efficient and means you won't have to push…
-
No, there's no display functionality SR can hook into on post functions. You need to trap the error and write it into a field on the issue.
-
Could you explain what this has to do with Confluence?
-
Then you'll need to go to the "create" url directly instead of the page you are on.
-
The admin pages show all projects,so just go to the list of issue type screen schemes.
-
Your reading is correct, it will replace config files and you'll need to re-do customisations. I think it reports on them as it runs, but I can't remember exactly when that was added to the scripts. I'd also say that you might not need to worry about 6.4.2 - although I would not recommend going from 6.3.anything or lower…
-
Older versions of Jira did not let non-administrators create projects. So you were an admin before. The latest version lets users create their own projects, but only of Agility type.
-
An SQL query is a pain - you would have to read every issue type screen scheme and screen scheme for the basic list of screens and where they are used, then the project configs to see which issue type screen schemes are in use where, and then read the whole workflow table parsing it for the screen ids in use in…
-
Create a new screen with the field "resolution" on it. Then edit your workflow and add a transition screen to the transition into done. The users will be prompted for the resolution when they close issues.
-
From memory, the JMWE functions all upgrade well - you just need to install the newer version of the add-on that is compatible with 5.2. Do it via "manage add-ons", as that will select an appropriate version for you. 5.2 is a long way off the latest version of Jira though, it's years old. 7.10 is out soon
-
Have a read through the release notes, they give you the new features. https://confluence.atlassian.com/bitbucketserver/bitbucket-server-release-notes-872139866.html
-
Question all the fields, every time. Why are they different to fields that already exist? What report relies on them so that they have to be separated out and can't be done in simple text? Do you really have 2,100 items that are all reported separately? I suspect you'll find 99% of them are useful to 1 or fewer people, and…
-
I don't think you're understanding this. What is the point? You are doing nothing that I can imagine being in the slightest bit useful by duplicating data that is already on the issue in front of the user. Why are you wasting your time with this?
-
Without having to build code and scripts, import the backup into a temporary dev system and read the system info, or go to the database.
-
The official way to do this is to export the system to xml, change the installation so it looks at the new database and import the xml.
-
The use of a simple custom field won't do what you are describing unless you have configured something to make it behave that way based on the field ocntent. What type of field is "team"?
-
I've only ever used the ones built into theming add-ons
-
Why? The links are already in the attachments area.
-
The "selected id" is not being stored because your code is changing it to something that is wrong. I can't tell you what is wrong with your code because it seems to be doing something that is nonsense. Could you describe exactly what you are trying to do?
-
You'll need an add-on to provide a "redirect" function.
-
Why don't you just use the attachments "field"?
-
Graphs can be used for any field they support. Jira's use of the resolution field to determine resolution is core to the product and cannot be changed at present.
-
We can't tell you how you would contact your mail admin - we know less about your email systems than you do.
-
That's something Microsoft need to fix in Smartscreen, not Atlassian.
-
Start by using a supported database - the latest versions of Confluence only support MySQL 5.6 and 5.7
-
Yes, you can report on any field you choose.
-
Sub-tasks are not "copied" when completing a sprint. They are part of their parent story and hence move into the next sprint as part of it.
-
What does the marketplace.atlassian.com entry for it say?