Comments
-
Hi Tamara, if these users have JSW licenses then you can add them to a group/role that has Browse permissions for the project. If they don't have ANY access to the Jira instance at all, e.g. Customers in JSD project then you can't share with them.
-
ok so with the original JSD Automation you can change the run rule as the rule level by clicking on the cog. Note: the user that is set to run the rule MUST have permissions in the project where the action is being performed.
-
Hi Chris, I think you are going to run into issues w/ IE TBH. I assume it is working for you in other browsers? supported-browsers
-
Which form of automation is involved here? In JSD there are two: Automation (at the top) and Project Automation (at the bottom). in JSW there is just the one Automation (which equates to (Project Automation in JSD...yes confusing). Can you chose the rule to run as the one that triggers the event?
-
Hi Manuelm, welcome to the Community. Could you provide some more info here so that I might better assist. Can you share a screenshot of your entire screen when you go to add the user? I'm trying to understand the type of project and how you are adding the user.
-
if they are a Jira admin you cannot hide it from them, only if they are a project admin.
-
This is simply changing the status to that which is driven by the transition. You cannot remove this BTW - how-to-remove-optional-post-functions-from-the-initial-transition-in-a-workflow
-
@Amir Barkal, i do not think you will get an estimate in this forum. Short of seeing an Atlassian convey that 'we are working on this now' or 'this is on our roadmap', I have never seem any commitment for feature schedule in the Community. Nor would I expect one TBH.
-
Hi Amy, this is certainly possible as Robert has eluded. However, to be able to assist you further we would need more info. Can you provide details ? The key here is to decide on how you wish to define your teams. For example, you might choose to create groups and add members to them. While this is most certainly doable it…
-
understand. So first, if your issue is not resolved by my response please uncheck the "answer accepted" as that should only be done once you are satisfied that an answer hits the mark. So let's dig into what is going on. Clearly something is automatically setting these fields. Where I was going with my initial 'answer' was…
-
Hi Carmen, let me restate what I think you are asking before I suggest a solution. Allow transition to “test in development environment" status only if the “development” field is empty. It also seems that there isn’t any restriction to transition to “test configuration” or are you saying the “development” field needs to be…
-
I wonder if the Resolution is getting auto populated at creation via a workflow faux pas.
-
If you are new to Jira it will be difficult for you to perform an adequate walk-through I think. Depending on your situation you might find an available video tutorial a good option. Here is a quick Google search - jira+cloud+tutorial+video
-
You can create a custom field of type People in NG. This is done on the Issue Type screen.
-
Hi Witalij, welcome to the Community. Exactly where are you seeing this? Maybe the Jira App or elsewhere. Based upon that it may not be possible (yet). There is an open suggestion that might be related to your inquiry - JRACLOUD-74711
-
p.s. please update here w/ anything you find out.
-
No worries Yossi. So yes as an admin you should be able to do just about anything. However, there can be conditions that restrict actions. In the case of Transitions you can place Conditions on them such that the transition will not be allowed unless the Condition(s) is met. Now this may not explain your issue but let's…
-
Permissions to transition issues by a customer is actually not done thru "permissions" but rather thru the workflow - exposing the transition or not - as you have discovered on your own.
-
Can you check the Reopened transition for any Condition that might explain this? For example maybe only the Assignee can do this.
-
I don't think the Community is going to be able to assist with this issue. Please reach out to Atlassian Support. BTW, this is a pretty old version of Jira so maybe that is coming into play here, just a crazy guess though.
-
In NG Epic Links don't really exist (as yet anyway).
-
Hi Anita, there are a number of ways to view this using Dashboard gadgets. One that comes to mind is the Created vs. Resolved. The only issue with this would be that you would need one for each developer so for a big team this could get busy. Another option is to look at the Two Dimensional gadget and set the X-axis to…
-
Cool so I definitely would report this to Atlassian Support. I expect this would turn into a bug/suggestion to be resolved.
-
I don't believe there is any way to control public comments at that granular level. Public comments go to all vested parties.
-
correct. There are addon solutions that could present a different portal solution altogether that is more customizable, e.g. Refined Themes. Or you could also create your own portal solution. Of course that is a bit of work.
-
you can set it up so that the comment reopens the issue which is likely what you want to have happen. This will ensure notifications occur.
-
Hi Mike, welcome to the Community. There isn't a way to combine/arrange multiple boards on one browser screen. You could consider create a single board that captured multiple projects. However, depending on the underlying workflows it might be a bit messy. If the workflows are fairly simply and similar then you could…
-
Excerpt from status.atlassian.com Issue with bulk editing issues Resolved - Between 03:00 UTC to 07:00 UTC, we experienced an issue with users unable to bulk edit issues for Jira. The issue has been resolved and the service is operating normally. Aug 10, 07:10 UTC
-
That is an interesting scenario. I have not used the comment contains condition previously. I may try to test this out when I have a moment. What do the automation Logs convey? Does it fail the condition? It may be that the automation logic can’t process comments with images (signature in this case). It might be worth…
-
This is not configurable