Comments
-
Notification schemes are usually based on Project Roles or Groups. The notification scheme should be modified so that only certain roles or groups get each of the notifications. See my answer below for how we do that.
-
Hi Marco, Maybe try removing the sub-filter completely just to see what happens? Then you can put it back in. Also, in what status are the Incident and Problem issues?
-
Hi Ran - Welcome to the Community! Yes, the Notification Scheme is the best route to go. I have very few things that send out notifications, and usually do that just for Reporters so they see when an issue is Closed or Deleted or Discarded. However, I pretty much have everything send a notification to Watchers. I have…
-
There are add-ons such as Automation for JIRA and ScriptRunner that will help you do that. But, again, adding a Transition screen specifically for the Description field might be the best and least costly solution.
-
You might try the work around mentioned here to see if that helps: https://jira.atlassian.com/browse/JRACLOUD-68558 * Change the field configuration to show the field Time Tracking (on your project and or issue type).
-
I am in Jira Cloud also and get the error when adding it as a Condition (and also do not see it for Validators). You should open a support ticket with Atlassian as this looks to be a bug to me.
-
I see the "Log work" field when I go to add a field to a screen. Maybe they have renamed the field? Have you tried to add a value to the issue to see if it shows up in the field when you do a query?
-
Hi Fred - are you trying to create an issue on the above project (CMS)? Or are you needing to create a whole new project? If it is the first, then you should contact one of the project administrators to grant you permission to create on the project. If you need a new project entirely, you should contact your Jira System…
-
Hi Avinash - Welcome to the Community! Yes, if the base filter for the board (or the sub-filter) excludes the Epics, then the quick filter will not work. Can you provide the filter (and sub-filter) for the board?
-
@Robert Campbell - understand that, too! We have about 70 workflows and well over 100 issue types that we are transitioning to about 10 workflows and the same number of issue types. We have lots of custom fields, too - and I know everyone says they are bad, but if they are helpful to the team, then I am okay adding them.…
-
You should open a support ticket with the Capture for Jira 3rd party vendor then.
-
Hi Smit.s You can still add a Validator to the transition to make the field required to move the issue to that status. You can also modify your validation to sub out the fields.
-
Hi Prashanth, We use an add-on called Cloud Files. It has been a huge help for us as you can create folders, sort differently, upload larger file sizes, etc. You will need an AWS S3 bucket to store the files in. Support is always very responsive and helpful.
-
Hi Ricardo, If you click on a transition you will see the pop-up box appear for options for that transition. Choose Validators. Then Add validator. When you get the list of Validator types, choose Field Required Validator. I hope that helps!
-
Hey Kyall, We use the JMWE add-on to do that in a post function.
-
Hi Bill, We use the Actionable Agile add-on right now for that. They have a fantastic chart for it.
-
That stinks. So do you get any error at all? Or is there just no column available to move it when you try to drag it? But you see the transition and can change statuses on the card itself? Does it happen for all statuses? Or just trying to move to certain statuses?
-
Hi Jakub, I assume by "initial state" you don't mean on Create. Otherwise, you could have a different create screen from the edit screen. You might consider using a Transition screen that makes sure the fields are populated before the transition can happen.
-
Hey Robert, I feel your pain. :-) Personally, I would consider the work to be Done when it hits the Awaiting Release status. In fact, I would just rename that to Done itself. But I would group the issues by Release, ie. populate the Fixed versions field with the release you created. Then when you actually release the code,…
-
Hi László - very sorry, but don't know what you tell you. Thought it might be something with trying to move from To Verify to Done since both are Done type statusCategory. Looks like you need to submit a support ticket with Atlassian. :-( Would be very interested in what the solution ends up being!
-
Hey Connie, I was able to run it with no problem. I am using the Cloud version. I might have something to do with the GDPR changes but not sure. If you are on Server, it might be a server version issue.
-
Yes, it can apply to any issue. Are you using the old JIRA issue view or the new one?
-
Hi Susmita - Welcome to the Community! If I understand it correctly, I would have the engineering director Move the US to the appropriate project instead of cloning the issue, which would create multiple copies of the same US. I hope that helps!
-
Great - thanks of sending that! Are there just certain columns you are having trouble dragging between? Or is it every column. And can you do one more screenshot - this time for the workflow?
-
Hi Hal, Workflows are the underlying backbone of how works through the organization for different issue types (work item types). They can support multiple projects and multiple boards. Therefore a board admin should not be able to change workflow because it might affect many other projects and boards.
-
Any way you can do a screenshot of your board settings showing your columns?
-
Wow, I am out of ideas then. You probably want to open a support ticket with Atlassian. :-(
-
Hi Dwight - Welcome to the Community! You will need to modify your Workflow first, if you haven't already, to add those statuses with the appropriate transitions. Once that is done, you should be able to modify your board to add the new columns and drag in the new statuses.
-
Great! Can you click on the Accept Answer so others can see.
