Comments
-
Hi @Brittany Joiner , I can successfully search using the "#" for labels. example - #Kitchen brings up all my cards that have the Kitchen label. I am using the Mac app.
-
yep i mispoke...it should have been Sprint Report. I have corrected in my original response for future searchers.
-
are you referring to issue on jira.atlassian.com? If so, assuming you are in fact the reporter then perform a search like this... watcher = currentUser() or reporter = currentUser()
-
first I would advise against deleting ANY issues in Jira. You cannot query on any deletions. That said, if your webhook works to update SP then you should be able to use any JQL so if you create the JQL I mentioned above it should provide you updates to existing issues. You can add more to the JQL to meet your needs.
-
:-( if you did a recent backup you could do a complete restore. that is the only way I'm afraid. Any changes since the backup will be lost when you restore.
-
i cannot say definitively (I don't work for Atlassian) but the pricing page I referenced has a check for apps and integrations. My bet is that it surely will. Easy enough to try and see.
-
Well if you can use Cloud then there is a free version. while it has some limitations it may very well work for you. https://www.atlassian.com/software/jira/pricing
-
how is your JQL going to update Sharepoint? You mention new issues created but then further in you mention any updates at all. What is your actual goal? can you provide the JQL that you say works for you w/ single project as a starting point? you could create a filter and subscription to run daily to show update w/in the…
-
i would have thought Project admin was sufficient but if you are a project admin and not seeing it then it must be Jira admin permissions. Are you able to get the Project Settings? If so look for Layout.
-
is the Assignee the same as the user triggering the issue? If so this is because of the "Do not notify me of my change". if someone other than the Assignee is invoking the transition I would expect the assignee to get notified even w/o the post function unless you have that notification disable which is something to…
-
go to the Reports section for the project. Select the report of interest, e.g. sprint report and select sprint from drop down.
-
if you are using the new issue view you can do it as follows. go to an issue that would otherwise have that field and click on the "Configure" link at the bottom right column. in the Configure screen you will see several sections. The lower shows fields that are hidden if empty. drag your field from there to the middle…
-
Great question Steven and unfortunately I have a mixed answer for you. For some time now I have understood and believed that there was metadata in the header in conjunction with the issuekey in the subject. In fact I had a discussion with an Atlassian on that very topic. Having said that I ran into a situation recently…
-
This is an often asked for feature in the Community and there are some active discussions on the topic. You will actually see so,e threads listed to the right here under “related content”. There has been no official announcement of this feature for server or data center. IMO, the solution for DC would be Portfolio. You…
-
I’m thinking you are going to be looking at an addon to alert specific users based on specific conditions. Automation for Jira is a great tool for this and if my understanding is accurate this will soon be integrated in Jira Cloud. If you can’t wait download the “Lite” version which is free and gives you 300…
-
@Stefan Meier , I think this is related to your other post . In this post you indicate “it works in filters”. Can you share your filter here?
-
Hi Stefan, Basically you need to translate the custom field ID to the name. You have to be an admin and navigate to the Custom Field list screen an use the translate button. * Jira settings > Issues > Custom fields * choose any field and click ellipses and Translate * in the URL you will see a number at the end * replace…
-
So I think I get what you are saying. It seems your process is that you create Epics with issues and when until you are ready to move the epic effort forward you leave it and all associated issues in To Do. So until the Epic moves to In Progress you want to hide all of the associated issues from your board. Assuming this…
-
Well creating a test user is easy but you first need to create a test email. If you are using say MS Exchange the your IT group would do this. You could also simply create a Gmail account and use that. Then you simply add that user email to a project or directly via Jira settings > User management > Users.
-
Check with your Jira admin. They can search under Jira settings > User management > users, and if necessary reactivate.
-
Thanks for the reference and confirmation Andrew.
-
There isn’t an obvious way with in Jira. I would suggest reaching out to your IT group as they typically own it. Most well formed IT groups will use Jira itself for internal requests (JSD). If so you could add an IT request to add users to Jira.
-
So on Cloud you cannot modify this unless something has changed. Note you must have the issuekey in the subject for Jira to recognize the issue and place a comment rather than creating a new issue. The [Jira] is not required for this to work but I don’t think this can be removed but will take a closer look.
-
Are you saying that the folks you are adding are not yet users in your Jira instance? If not then your Jira admin would need to add them first. If they are already users then assuming you are on a next-gen project you should go to project settings > access?
-
And then you can use quick filters for secondary and tertiary assignees but that isn’t very scalable.
-
correct ... you need to go to Jira settings > Issues > Priorities and edit each priority to capture the actual issue ID then use that specific number rather than the 'priority number'.
-
This is not possible. A customer could Cc (optional) the other person and mention in the description that they are raising on behalf of the other person. In turn the agent could then change the reporter (swap the reporter and request participant) as a work-around.
-
Does the issue get created and simply not go into a queue? If so, edit your queue where you wish to have it appear and inspect why it is being excluded and edit accordingly. If however, the issue is not even being created that is a different story. Please clarify.
-
that field isn't available in the default automation. you could achieve using Automation for Jira if that is an option.
-
No the burndown focuses on undone vs. done only. every status that is NOT in the right-hand most column of your board is considered undone